Skip to main content
Glama

Konfirmu

konfirmu_buscar_ficha

Procura nas fichas oficiais da Konfirmu (read-only) por tema e país. Devolve excerto literal, fontes com URL e o que NÃO garante. Sem ficha = diz que não há, nunca inventa.

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": {
      "termo": "<termo>"
    },
    "name": "konfirmu_buscar_ficha"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNoCódigo do país, opcional (ex.: NL, PT, DE, FR).
termoYesO que procuras, em palavras simples (ex.: «carteira perdida», «casa do patrão», «fatura»).
limiteNoMáximo de fichas (por omissão 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does meaningful work: it declares read-only access, describes the return payload (literal excerpt, sources with URL, and explicitly what is NOT guaranteed), and commits to a negative-result behavior (says there is none rather than fabricating). It stops short of auth/permission or coverage-scope details, which keeps it below 5.

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?

Three compact sentences: purpose, return shape, edge-case behavior. Front-loaded with the action and the source of truth, with no filler or repetition of the tool name.

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 three simple flat parameters, all schema-documented, and no output schema, the description usefully fills the gap by describing what comes back and how the empty case behaves — the two things an agent most needs before calling. Missing only peripheral detail such as corpus coverage limits or language handling.

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%, so all three parameters (termo, pais, limite) are already documented in the schema, including the example country codes and the limit bounds. The description only restates 'por tema e país' at a high level and adds no format, normalization, or matching-semantics guidance beyond the schema. 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 specific verb ('Procura') and a specific resource ('fichas oficiais da Konfirmu') plus the two search axes (tema and país). The scope is narrow enough to separate it from konfirmu_limites and konfirmu_ata_construir, though it never names a sibling to contrast against explicitly.

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: consult this when you need an official sourced answer on a topic/country. There is no explicit when-not-to-use clause, no mention of falling back to another sibling tool, and no stated prerequisite or rate limit. 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