Skip to main content
Glama

BitTalk News

fetch

Read-onlyIdempotent

Full document by id from search: forecast:BTC or news:.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restatement. The description adds the id namespace convention (forecast:/news: prefixes), which is genuinely useful, but says nothing about missing-id behavior, result size, or document structure.

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

Conciseness4/5

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

One compact sentence with the payload (full document by id) front-loaded and format examples trailing. Very little waste, though the telegraphic phrasing around 'from search' takes a moment to parse.

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

Completeness4/5

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

For a one-parameter read tool with annotations covering safety and no output schema, the description gives enough to construct a valid call. Remaining gaps, such as what the returned document looks like or what happens on an unknown id, are minor.

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

Parameters4/5

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

Schema coverage is 0% and the single parameter is bare 'Id', so the description carries the full burden. It does so reasonably well by giving two concrete id formats with the required prefixes, though it leaves the news id's numeric range and any other prefixes unstated.

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

Purpose4/5

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

"Full document by id" states a specific verb and resource, and the two examples (forecast:BTC, news:<number>) make the retrieval scope concrete. It is distinguishable from siblings like search or latest_news, though the name 'fetch' alone conveys nothing.

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

Usage Guidelines3/5

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

"from search" implies the intended workflow: obtain an id via the search tool, then call fetch to expand it. That is usage context by implication only; there is no explicit statement of when not to use it or which sibling to prefer for non-id lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources