Skip to main content
Glama

edge-signals

crypto_brief

Crypto news brief: ranked headlines with source URLs and heuristic sentiment. Topics: crypto, base, defi.

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

Input Schema

NameRequiredDescriptionDefault
topicNocrypto (default), base, or defi

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?

With no annotations, the description carries the burden, and it does disclose useful traits: output is ranked, includes source URLs, and sentiment is explicitly labeled heuristic (a meaningful trust caveat). It omits recency/freshness window, how many headlines are returned, and any rate-limit or caching behavior for what is presumably a live external feed.

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?

One sentence, front-loaded with the resource and followed immediately by the return shape. Nothing is padded, and the topic list at the end is short enough not to bloat it.

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 low-complexity read tool with one optional parameter and no output schema, explaining the returned fields (headlines, URLs, sentiment) is the essential content and it is present. The only real gap is freshness/latency, which matters for a news feed.

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% and the single parameter already documents 'crypto (default), base, or defi'. The description repeats the same three values without adding format, case-sensitivity, or fallback behavior for an invalid topic. Baseline 3 is correct when the schema does all the work.

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?

States a concrete resource (crypto news brief) and enumerates what the caller gets back: ranked headlines, source URLs, and heuristic sentiment. That is far more specific than a name restatement, and it is implicitly distinct from the entirely on-chain siblings (balances, gas, odds, funding). It stops short of an explicit 'this is the only news tool' framing, so a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied by 'Crypto news brief', which an agent can reasonably map to informational/news requests rather than price or wallet queries. Adequate but leaves routing to inference.

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