Skip to main content
Glama

BitTalk News

latest_news

Read-onlyIdempotent

Latest BitTalk News articles (Russian-language source): title, date, rubric, link and first paragraph.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "latest_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
rubricNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context by disclosing that the source is Russian-language and by listing the returned fields, which matters since there is no output schema. It omits ordering guarantees, pagination, and what happens when no articles match.

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?

A single front-loaded sentence that identifies the source, the scope, and the payload with no filler. Nothing in it could be cut without losing information.

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?

Because there is no output schema, the enumerated return fields are a real asset and largely close the return-value gap. However, with two undocumented parameters and no indication of valid rubric values or result ordering, an agent can call it but cannot call it well.

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 coverage is 0%, so the description carries the full burden for the two parameters. It mentions 'rubric' only as a returned field, never explaining that it is an input filter or what values it accepts, and it says nothing about what 'limit' controls or its bounds.

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?

The description names the resource precisely (BitTalk News articles) and characterizes the scope as 'latest', plus enumerates the returned fields (title, date, rubric, link, first paragraph). It never names the obvious alternative, search_news, so the agent must infer the recency-vs-query distinction from the word 'Latest' alone.

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?

Usage is only implied: 'Latest' signals a browse-recent-feed operation rather than a targeted query, which contrasts implicitly with the search_news sibling. There is no explicit when-to-use, when-not-to-use, or routing statement, and no note about the Russian-language source limiting applicability.

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