Skip to main content
Glama

Listar radar

listar_radar
Read-onlyIdempotent

Briefings de engenharia reescritos pela Rota Nacional, com o link da fonte e o teste grátis. Público. Todo o histórico público dos bookmarks, inclusive os que renderam Guia. O modelo decide quando há orientação útil ao RN; segurança fica em Cyber. Navegue por page ou leia /pt/radar/feed.json e /pt/radar/feed.xml. Páginas /pt/radar/ e /en/radar/.

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

Input Schema

NameRequiredDescriptionDefault
pageNoA página, de 1 em diante. Vinte peças por página, até o fim do acervo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely new behavior — the content is fully public, it spans the entire bookmark history including items that became Guia, and the same data is reachable via feed.json/feed.xml as well as pagination. It does not describe result ordering or what a page payload looks like, but with no output schema that is a minor omission for a simple public read.

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

Conciseness3/5

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

It is short, but it is a run-on sequence of unrelated statements — content description, licensing note, historical scope, a model-discretion remark, feed endpoints, then page paths — with no front-loaded purpose sentence. The final line about `/pt/radar/` and `/en/radar/` largely repeats the feed-endpoint sentence and could be merged or dropped.

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-optional-parameter, read-only listing tool with no output schema and annotations covering safety, the description supplies what matters: what the corpus contains, how public it is, how far back it goes, and alternate retrieval channels. The only real gap is that it never says what an individual radar entry contains structurally, though the opening clause hints at source link plus free-trial reference.

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 description coverage is 100% and the single optional page parameter is already documented as 1-based with twenty items per page. The description only echoes "Navegue por page" without adding format, bounds, or default behavior, so it contributes nothing beyond the schema and the baseline of 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 identifies the resource concretely — engineering briefings rewritten by Rota Nacional, with source links and a free-trial mention — and explicitly routes security content elsewhere ("segurança fica em Cyber"), which distinguishes it from listar_cyber. It never states a clean verb+object like "lists radar items", so the purpose must be assembled from scattered fragments rather than read in one clause.

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 one real routing rule (security goes to Cyber) and an access-method note (paginate with page, or read the JSON/XML feeds), which is useful. However, nothing states when an agent should choose listar_radar over siblings like listar_guias or listar_novidades, and the phrase "O modelo decide quando há orientação útil ao RN" pushes the decision back onto the caller without criteria.

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