Fix context7 MCP server configuration: correct tool names and description

[Copilot]

The context7 shared workflow configuration referenced a non-existent tool get-library-docs and mischaracterized the service as a "vector database" when it's actually a library documentation provider.

Changes

Tool names (.github/workflows/shared/mcp/context7.md):

• Changed get-library-docs → query-docs to match actual Context7 API
• Retained resolve-library-id (correct)

Description and documentation:

• Updated purpose from "Vector database and semantic search" to "Up-to-date code documentation for any library"
• Added clarifying details about fetching version-specific docs and preventing hallucinated APIs
• Added usage examples:

  "Create Next.js middleware that checks for JWT. use context7"
  "Implement authentication with Supabase. use library /supabase/supabase for API and docs."

Compiled changes:

• Recompiled workflows to propagate tool configuration to lock files
• mcp-inspector.lock.yml now references correct query-docs tool

Reference: Context7 GitHub Documentation

Original prompt

Review context7 shared agentic workflow against the context7 project documentation. Double check it is properly configured.

Custom agent used: technical-doc-writer
AI technical documentation writer for GitHub Actions library using GitHub Docs voice

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.