Skip to main content
Glama

Dilligence — certidões de empresas

Lembrar pedido por e-mail

remind_request

Manda de novo o e-mail de um pedido a uma pessoa, com o que ainda falta (id de list_requests). Só se o usuário pediu.

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": {
      "request_id": "<request_id>"
    },
    "name": "remind_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses the externally visible effect (an e-mail is sent again to a person), consistent with openWorldHint=true and idempotentHint=false. However, it never says how the recipient is determined when the only parameter is request_id, nor what happens if nothing is pending or the send fails — meaningful gaps for a non-idempotent external action.

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?

One compact sentence plus a gating clause, front-loaded with the action and its payload. The telegraphic phrasing is efficient, though the parenthetical id hint is slightly buried at the end.

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 single-required-parameter tool with no output schema, the description covers the action, the payload, the id source and the user-consent gate. It is not complete on recipient identity or success/failure behavior, which an agent would still need to reason about.

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 carry the load; it does add real value by stating the id comes from list_requests. It says nothing about expected type/format or what happens with an invalid or stale id, so compensation is incomplete.

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?

"Manda de novo o e-mail de um pedido" gives a specific verb (resend) and resource (request e-mail), plus the extra detail that the message carries what is still outstanding. It stops short of naming a contrasting sibling operation (e.g. create_request or request_documents), so differentiation is only partial.

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?

"Só se o usuário pediu" is an explicit precondition that gates invocation on an explicit user request, which is the key guardrail for an outbound e-mail. It also points to list_requests as the source of the id. No when-not conditions or alternative tools are described beyond that.

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.