Skip to main content
Glama

Dilligence — certidões de empresas

Esperar mudanças

wait_for_changes
Read-onlyIdempotent

Espera até 45 s por mudanças na diligência. Passe o cursor devolvido na chamada anterior. Repita enquanto houver itens fetching ou waiting.

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": {
      "id": "<id>"
    },
    "name": "wait_for_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a 45-second blocking window and the polling-loop termination condition. It does not say what happens on timeout with no changes, which keeps it from a 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 short sentences, front-loaded with the 45-second bound, then the cursor mechanic, then the loop condition. No filler and nothing repeated from the schema.

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?

With no output schema, the description should say what a call returns — it only hints that a cursor comes back and never mentions the changed items or the fetching/waiting statuses it references. Adequate for a polling helper, but an agent cannot fully predict the response shape.

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 0%, so the description must compensate. It does explain 'cursor' (the value returned by the prior call), which is the non-obvious parameter, but the required 'id' is never identified as the diligence identifier and the optional nature of cursor is left implicit.

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 gives a specific verb and resource — wait up to 45 s for changes on a diligence — which clearly separates it from plain read siblings like get_diligence or list_diligences. It does not explicitly name an alternative, but the wait/poll nature of the tool 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 Guidelines4/5

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

It states a clear usage protocol: pass the cursor returned by the previous call and repeat while items are 'fetching' or 'waiting'. That is a concrete when-to-use/loop condition, though it never says when to stop using this and call get_diligence or get_item instead.

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.