Skip to main content
Glama

noticias

Read-onlyIdempotent

Retrieves UFC news and notices by reading official RSS feeds from UFC Informa, PROGRAD, and PRAE, with source filters and result limits.

Instructions

Lê os feeds RSS oficiais de notícias e editais da UFC (UFC Informa, PROGRAD e PRAE). Os campos texto_externo são conteúdo de terceiros.

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

Input Schema

NameRequiredDescriptionDefault
fonteNotodas
limiteNo
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds useful provenance context by flagging texto_externo as third-party content, but it omits the refresh/caching semantics implied by atualizar.

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 purpose front-loaded and no wasted wording. The third-party content caveat is appended efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be described, and three defaulted params keep the tool simple. However, without param explanations (notably atualizar's caching/refresh behavior), the definition leaves gaps an agent would want filled before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is expected to compensate, yet it says nothing about fonte, limite, or atualizar. The fonte enum (todas/ufc/prograd/prae) is somewhat self-explanatory and defaults are in the schema, but the meaning of limite and especially atualizar (caching/refresh behavior) goes unexplained.

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 uses a specific verb ("Lê") and names the exact resource and sources: RSS feeds of UFC Informa, PROGRAD, and PRAE. An agent can tell this reads official news/notices, distinguishing it from sibling tools like alertas or avisos, though it doesn't explicitly contrast them.

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?

Usage is implied by the sources listed (reading official UFC news and notices), but there is no explicit when-to-use or when-not guidance versus similar-looking siblings such as alertas, avisos, or agenda. The agent must infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.