Skip to main content
Glama

Dilligence — certidões de empresas

Ver pedidos

list_requests
Read-onlyIdempotent

Pedidos do workspace: a pessoas (link de envio; quem abriu, lembretes) e aos órgãos (cada busca), com o que já chegou. Use para acompanhar e cobrar.

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

Input Schema

NameRequiredDescriptionDefault
open_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that results include the send link, who opened it, reminder state, and what has already arrived, which is useful status context beyond the annotations, but it says nothing about volume, ordering, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the content of the listing, with the usage sentence at the end. The phrasing is terse and ambiguous in places ('aos órgãos (cada busca)'), so brevity comes at the cost of readability.

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

Completeness2/5

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

For a tool with no output schema and an undocumented parameter, the description should clarify the filter and the shape of results. It gestures at the data categories but leaves the agent unable to determine what open_only does or how results are organized.

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?

The single parameter open_only has 0% schema description coverage, and the description never mentions it. Because schema coverage is low, the description was the only place to explain what 'open' means and how it filters the two request types, and it fails to do so.

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

Purpose3/5

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

The description characterizes what the listing contains (requests to people and to agencies, plus what has arrived), which hints at a list operation, but never states the verb 'list' or 'view' explicitly. It is distinguishable from create_request and remind_request only indirectly, through the notion of tracking status.

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?

'Use para acompanhar e cobrar' gives an implied usage context: tracking and chasing outstanding requests. However, it does not name alternatives such as remind_request (which is presumably the tool for actually sending reminders) or list_diligences, leaving the agent to infer the boundary.

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.