Skip to main content
Glama

get_news

Latest crypto news (CoinDesk, CoinTelegraph): title, source, link and date.

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": "get_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many news items (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It helpfully identifies the news sources (CoinDesk, CoinTelegraph) and the returned fields, but does not clarify freshness semantics, authentication requirements, rate limits, or whether results are cached. It adds some context but leaves key behavioral traits unspecified.

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, front-loaded sentence that efficiently names the resource, sources, and returned fields with no wasted words. It is appropriately sized for a simple retrieval tool.

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 retrieval tool with no annotations or output schema, the description provides enough context to call it correctly: it identifies the data sources and the fields returned. It could be slightly more complete by noting the default result count or freshness behavior, but the schema covers the limit parameter.

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

Parameters3/5

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

The only parameter is 'limit', and the schema provides 100% description coverage including default (15) and allowed range (1-30). The description does not mention the parameter at all, so the schema does all the work; the baseline of 3 is appropriate.

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 states a specific resource ('Latest crypto news') and lists the returned fields (title, source, link, date), making the tool's purpose clear. It does not explicitly differentiate itself from siblings, but the news domain is distinct enough that an agent can identify it without confusion.

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?

The phrase 'Latest crypto news' implies the tool is used for retrieving recent news, but there is no explicit guidance on when to use it versus alternatives or any exclusions. Usage is only implied by the resource name and cannot be inferred beyond that.

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