Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_sources

Retrieve news sources by category and country through the Multi-MCPs server's unified API aggregation platform.

Instructions

List news sources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo
countryNo

Implementation Reference

  • The main handler function for the 'get_sources' tool. It validates the API key, extracts optional category and country parameters from input args, and delegates to the NewsApiClient's sources method to fetch the list of news sources.
    async get_sources(args: Record<string, unknown>) {
      if (!cfg.newsApiKey) throw new Error("NEWS_API_KEY is not configured");
      const category = args.category ? String(args.category) : undefined;
      const country = args.country ? String(args.country) : undefined;
      return client.sources(category, country);
    },
  • The registration of the 'get_sources' tool within the registerNewsApi() function's tools array, including its name, description, and input schema.
    {
      name: "get_sources",
      description: "List news sources",
      inputSchema: {
        type: "object",
        properties: {
          category: { type: "string" },
          country: { type: "string" },
        },
      },
    },
  • The input schema for the 'get_sources' tool, defining optional string parameters for category and country.
    inputSchema: {
      type: "object",
      properties: {
        category: { type: "string" },
        country: { type: "string" },
      },
    },
  • The supporting 'sources' method in NewsApiClient class that makes the actual API request to NewsAPI's /v2/top-headlines/sources endpoint.
    sources(category?: string, country?: string) {
      return this.request("/v2/top-headlines/sources", {
        headers: { Authorization: `Bearer ${this.apiKey}` },
        query: { category, country },
      });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List news sources' implies a read-only operation, but it does not disclose any behavioral traits such as rate limits, authentication needs, pagination, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just three words, front-loading the core purpose without any wasted text. It is appropriately sized for a simple tool, though this brevity contributes to gaps in other dimensions. Every word earns its place by directly stating the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It does not explain the parameters, return values, or behavioral aspects, leaving the agent with insufficient information to use the tool effectively. The conciseness comes at the cost of missing essential contextual details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has two parameters ('category' and 'country') with 0% description coverage, meaning they are undocumented in the schema. The description 'List news sources' does not mention these parameters at all, failing to add any semantic meaning beyond the schema. With low schema coverage, the description does not compensate, leaving parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List news sources' clearly states the verb ('List') and resource ('news sources'), providing a basic understanding of the tool's function. However, it lacks specificity about what 'news sources' entails (e.g., publishers, outlets, feeds) and does not differentiate from sibling tools like 'search_news' or 'get_top_headlines', making it somewhat vague. It avoids tautology by not just restating the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'search_news' or 'get_top_headlines', nor does it specify contexts or exclusions for usage. This leaves the agent without direction on tool selection, relying solely on the tool name and basic purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server