MCP Automations

daily_digest

Search the web for recent news on topic and return a digest with citations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "daily_digest"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes
`n_results`	No

Output Schema

Name	Required	Description	Default
`cost`	Yes
`items`	Yes
`topic`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It explains it searches and returns a digest with citations, implying a read-only operation, but does not explicitly state safety, rate limits, or other side effects. The 'recent news' and 'citations' details add some transparency beyond the schema.

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 a single sentence with no fluff, front-loading the action and purpose. It earns every word, though it omits parameter details (captured elsewhere in scoring).

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

Completeness3/5

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

Given the tool's simplicity, an output schema exists, and the core behavior is stated. However, the description omits the second parameter and provides no usage context relative to siblings. It is adequate but not comprehensive.

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?

Schema description coverage is 0%. The description only explains 'topic' via backticks, and does not mention 'n_results' at all. Since there are only two parameters and the description leaves one undocumented, it fails to fully compensate for the lack of schema descriptions.

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

Purpose5/5

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

The description clearly states a specific verb ('Search') and resource ('the web for recent news'), and clearly distinguishes this tool from siblings like find_competitors and summarize_url by focusing on news digests with citations.

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 is provided on when to use this tool versus alternatives, nor any exclusions. The description merely states what it does without specifying contexts or distinguishing it from similar search-based sibling tools.

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

All MCP Automations tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.