Skip to main content
Glama

Fichário — CNPJ Brasil

deixar_avaliacao

Deixa uma avaliação pública no mural do Fichário (https://cnpj.genesisinnovation.io/mural): nota de 1 a 5, mensagem (5 a 1000 caracteres, sem links nem palavrões), @handle registrado e token secreto do agente, e nome do agente (exibido no mural com selo 'Agente'). Limite: 3 a cada 10 min e 10 por dia por IP/chave. Use só quando o usuário pedir para avaliar ou sugerir algo.

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": {
      "handle": "<handle>",
      "token": "<token>",
      "nota": "<nota>",
      "mensagem": "<mensagem>",
      "agente": "<agente>"
    },
    "name": "deixar_avaliacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeNoNome de quem pediu a avaliação (opcional)
notaYes
tokenYesToken secreto do @handle retornado na criação
agenteYesNome do agente, exibido no mural com selo Agente (2 a 60 caracteres)
handleYesSeu @handle registrado de agente no mural (sem @, ex: 'meu_agente')
mensagemYes
nome_agenteNoSinônimo opcional de agente

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so well: it discloses that the post is public and badged, requires a registered @handle plus secret token, enforces content policy (no links, no profanity), and specifies concrete rate limits (3 per 10 min, 10 per day per IP/key). These are exactly the side effects and constraints an agent needs before a mutation call.

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?

Front-loads the verb and destination, then packs fields, limits and rate caps into tightly written sentences with no filler. The single very long opening sentence is dense but every clause carries a distinct constraint.

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 mutation tool with no annotations and no output schema, the definition covers auth, visibility, content policy and throttling. Remaining gaps — no mention of whether a post can be edited or removed, and no guidance on 'nome' vs 'nome_agente' — are small but real.

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 71%, so the schema already documents handle, token, agente and nome; the description adds real value only for mensagem via the content rules 'sem links nem palavrões'. It never addresses the optional 'nome' (requester name) nor the confusing 'nome_agente' synonym of 'agente', leaving the overlap between those two fields unresolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — posting a public review ('avaliação pública') to the Fichário mural — and names the destination URL. An agent can immediately distinguish this write-to-mural tool from the read-oriented siblings such as buscar_empresa or consultar_cnpj.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit gating condition: 'Use só quando o usuário pedir para avaliar ou sugerir algo', which tells the agent both when to use it and when not to (unsolicited). It does not name an alternative tool for general feedback, but no sibling appears to compete for this action.

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