Skip to main content
Glama

Listar cyber

listar_cyber
Read-onlyIdempotent

Briefings de cibersegurança e notícias reescritos pela Rota Nacional, no ângulo de prompt, documento e chave. Público. Todo o histórico Cyber, sem notícias gerais da Inova e sem gerar Guias. Navegue por page ou leia /pt/cyber/feed.json e /pt/cyber/feed.xml. Páginas /pt/cyber/ e /en/cyber/.

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_cyber"
  }
}

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

B3.4/5.0
Behavior3/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 scope context beyond that: the content is public, it spans the entire Cyber history, and guide generation is out of scope. It says nothing about auth requirements, rate limits, or what a feed read returns versus a page 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 and front-loads the resource, which is good, but it is a compressed run of fragments rather than sentences, and the jargon phrase 'no ângulo de prompt, documento e chave' consumes space without conveying a usable constraint. The trailing URL list ('Páginas `/pt/cyber/` e `/en/cyber/`') is unlabeled and of unclear actionable value.

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 read-only paginated list tool with one optional parameter, no output schema, and annotations covering safety, the description supplies scope, exclusions, pagination guidance and alternate feed endpoints. Only the unlabeled language-path fragment and the missing statement of return shape or page-size limits keep it from being fully complete.

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?

The single parameter has 100% schema description coverage, including the 20-items-per-page detail and the 'up to the end of the archive' bound. The description repeats the pagination idea and the feed alternative but adds no format or edge-case meaning 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?

States a concrete resource: cybersecurity briefings and news, and scopes it as the complete Cyber archive. It also explicitly excludes general Inova news and Guide generation, which helps separate it from siblings like listar_novidades and listar_guias. The verb is only implied ('Briefings de cibersegurança e notícias...'), and the phrase 'no ângulo de prompt, documento e chave' is opaque, but the subject matter is unmistakable.

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?

Tells the agent to navigate by page or to read the JSON/XML feeds, which is a real usage hint, and gives two exclusion rules (no general Inova news, no Guides). However, it never names a sibling tool to use instead, so the routing between listar_cyber and listar_novidades is left to inference from the exclusions alone.

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