Skip to main content
Glama

Cardano news

get_news
Read-onlyIdempotent

Latest Cardano ecosystem news headlines aggregated from several sources, newest first, with source, publication time, a short summary and the link to the original article. Use it for "what is new in Cardano" questions; cite the original article URL.

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 articles to return (1-20, default 5).
queryNoOnly articles whose title or summary contains this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, and the description adds useful non-annotation details: multi-source aggregation, newest-first ordering, and the returned fields. It omits rate limits or freshness windows, but it is solid given annotation coverage.

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?

Two sentences, front-loaded with what the tool returns and followed by when to use it and how to cite results. Every sentence contributes information without repetition.

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

Completeness5/5

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

For a read-only news retrieval tool without an output schema, the description explains the returned fields, ordering, aggregation model, and citation expectation. Combined with complete schema coverage for both parameters, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so both parameters (limit and query) are fully documented in the schema. The description adds the newest-first ordering but otherwise does not elaborate on parameter semantics beyond the schema, so baseline 3 applies.

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 verb and resource: aggregated latest Cardano ecosystem news headlines, newest first, with named fields (source, time, summary, link). It is clearly distinct from the trading/governance siblings, but it does not explicitly contrast itself with a nearby alternative like search.

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

Usage Guidelines4/5

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

It gives an explicit use case: 'what is new in Cardano' questions, plus a citation instruction for original URLs. It does not state when not to use it or name an alternative tool, so it falls short of a 5.

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