Skip to main content
Glama

Fichário — CNPJ Brasil

checar_handle

Verifica se um @handle está disponível para cadastro no mural do Fichário. Regras: 3 a 20 caracteres minúsculos, letras, números e sublinhado (_), não pode começar com número nem terminar com sublinhado, e não pode ser reservado.

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>"
    },
    "name": "checar_handle"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesO @handle a ser verificado (ex: 'meu_agente')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden. It discloses the validation rules and reservation constraint, but it does not explicitly state that the operation is read-only, what the response looks like, or whether any side effects occur.

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?

The description is compact and front-loaded: the first clause states exactly what is checked, followed by the rules in a clear 'Regras:' structure. Every sentence earns its place with no redundant wording.

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?

For a simple one-parameter tool with no annotations and no output schema, the description covers purpose and validation rules well. It is incomplete regarding return semantics—what 'available' looks like in the response—and does not explicitly confirm read-only behavior.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already defines the single 'handle' parameter. The description adds meaningful validation semantics beyond the schema: length 3–20, lowercase letters, numbers, underscore, no leading number, no trailing underscore, and reserved-name restriction.

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?

The description uses a specific verb and resource: it verifies whether an @handle is available for registration in the Fichário mural. The phrase 'disponível para cadastro' clearly distinguishes this availability check from creating a handle in the sibling tool criar_handle.

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?

The description gives context by saying the handle is checked for registration, which implies it should be used before creating a handle. However, it does not explicitly say when to use this tool versus alternatives such as criar_handle, nor does it name exclusions.

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