Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

search_news

Search news articles by query and date range to find relevant information from aggregated sources.

Instructions

Search news articles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
from_dateNo
to_dateNo

Implementation Reference

  • The handler function that implements the core logic of the 'search_news' tool. It validates the API key and query parameter, extracts optional date parameters, and delegates to the NewsApiClient's search method.
    async search_news(args: Record<string, unknown>) {
      if (!cfg.newsApiKey) throw new Error("NEWS_API_KEY is not configured");
      const query = String(args.query || "");
      if (!query) throw new Error("query is required");
      const from_date = args.from_date ? String(args.from_date) : undefined;
      const to_date = args.to_date ? String(args.to_date) : undefined;
      return client.search(query, from_date, to_date);
    },
  • The input schema for the 'search_news' tool, specifying a required 'query' string and optional 'from_date' and 'to_date' strings.
    inputSchema: {
      type: "object",
      properties: {
        query: { type: "string" },
        from_date: { type: "string" },
        to_date: { type: "string" },
      },
      required: ["query"],
    },
  • The tool registration object for 'search_news' within the registerNewsApi() function, which includes name, description, and input schema.
    {
      name: "search_news",
      description: "Search news articles",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string" },
          from_date: { type: "string" },
          to_date: { type: "string" },
        },
        required: ["query"],
      },
    },
  • Invocation of registerNewsApi() in the central registerAllTools() function, which includes the 'search_news' tool among others.
    registerNewsApi(),
Behavior1/5

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

With no annotations provided, the description carries full burden but offers zero behavioral disclosure. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, result format, pagination, or any side effects. This is inadequate for a search tool.

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 at three words with no wasted text. It's front-loaded with the core action, though this brevity comes at the cost of completeness. Every word earns its place by stating the essential function.

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

Completeness1/5

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

Given the tool's complexity (search with 3 parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It fails to provide necessary context about behavior, parameters, or results, making it inadequate for effective use.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no parameter information beyond what the schema names imply. It doesn't explain what 'query' should contain, date format for 'from_date'/'to_date', or default behaviors. With 3 parameters (1 required) and no schema descriptions, this is a significant gap.

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 'Search news articles' states the basic purpose (verb+resource) but is vague about scope and lacks differentiation from siblings. It doesn't specify what kind of search (full-text, keyword, semantic) or what sources are included, making it less specific than ideal.

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?

No guidance on when to use this tool versus alternatives like 'get_top_headlines' or 'get_sources' is provided. The description offers no context about appropriate use cases, prerequisites, or exclusions, leaving the agent with minimal direction.

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