Skip to main content
Glama

PolySignals.net

Crypto news with live calls

get_news
Read-only

The latest crypto headlines from CoinArticle, newest first, each with the live overall Buy/Sell/Hold call of every tracked coin it names. Pass coin to keep only headlines that name it.

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
coinNoOnly headlines naming this coin
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral value beyond that: results are recency-ordered, headlines carry live per-coin calls, and the coin parameter filters rather than searches. It omits whether results paginate and what the limit cap means.

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 tight sentences: the primary behavior leads, the optional filter follows. Every clause carries information; nothing is filler.

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 two-parameter read-only tool with no output schema, it conveys the return shape (headlines plus live calls) and ordering. Minor gaps remain around the limit parameter and pagination, but an agent can 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 50%: coin is documented in the schema and restated in the description, while limit is undocumented in both places (default 10, max 20). The description compensates for the filter semantics but leaves the limit parameter unexplained, so it sits at the baseline.

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?

Names the specific resource (crypto headlines from CoinArticle), the ordering (newest first), and the enrichment payload (live Buy/Sell/Hold call per named coin). No sibling overlaps with news, and the scope is unmistakable in one read.

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?

Explains the coin filter's effect ('keep only headlines that name it'), which implies when to use it. But it never says when to prefer this over get_coin_signal or get_trend_changes, nor any exclusion conditions. Usage is implied rather than guided.

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