Skip to main content
Glama

One radar with headlines

get_radar
Read-only

Full feed of one radar: ranked headlines with source, time, weight and link, plus risk index and severity. The crypto radar also returns live Kraken prices for BTC, ETH and XRP in EUR.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "radar": "<radar>"
    },
    "name": "get_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNode adds title_de: a machine German translation of each headline (the original stays in title)
limitNoMax headlines (default 10)
radarYesRadar id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "de adds title_de: a machine German translation of each headline (the original stays in title)",
      +  "enum": [
      +    "de"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / radar / enum
      Previous value: -[
      -  "geo",
      -  "politics",
      -  "economy",
      -  "budget",
      -  "crypto",
      -  "energy",
      -  "web"
      -]New value: +[
      +  "geo",
      +  "politics",
      +  "economy",
      +  "budget",
      +  "crypto",
      +  "energy",
      +  "justice",
      +  "web"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and live-data nature are covered. The description adds genuine value by disclosing the record shape and the conditional crypto payload, which is behavior annotations cannot express. It still omits freshness/caching and whether the ranked list can be incomplete relative to limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, with the core payload described first and the conditional crypto note second. No filler, though the second sentence is a special case that could be compressed.

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?

With no output schema, the description does the necessary work of describing returned fields and one special-case return. For a read-only single-resource fetch with fully documented parameters, that is nearly complete, missing only ordering/freshness nuance.

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%, with enums for radar and lang and a documented default and range for limit, so the schema carries parameter meaning. The description adds nothing about lang or limit and only mentions the crypto radar's side effect indirectly, so the 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 opens with a concrete verb+resource phrase ("Full feed of one radar") and enumerates the payload: ranked headlines with source, time, weight and link, plus risk index and severity. The scope word "one" implicitly separates it from a list-style sibling, but no sibling is named, so the differentiation is inferred rather than stated.

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?

It says what you get for a single radar and notes the crypto-specific extra (live Kraken prices in EUR), which helps pick the right radar id, but there is no explicit when-to-use, when-not, or comparison to an alternative tool. Usage is only implied by the singular scope.

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.