Skip to main content
Glama

Dilligence — certidões de empresas

Conferir pagamento

check_payment
Idempotent

Confere se o usuário pagou o link de buy_credits e credita o saldo (uma vez só). Devolve paid, credited e o saldo atual em créditos.

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": {
      "session_id": "<session_id>"
    },
    "name": "check_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds genuine context beyond that: the call has a side effect (crediting balance) that happens only once, which reassures the agent that repeated calls will not double-credit. It does not mention permission or session requirements, which is a minor gap.

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?

Two short sentences with zero waste: the first states the action and the side effect, the second states the return values. The most important information (checking payment and crediting once) is front-loaded.

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?

With no output schema, the description usefully enumerates the returned fields (paid, credited, and current credit balance), which an agent would otherwise have to guess. Combined with annotations covering the mutation/idempotency profile, this is nearly complete, though it says nothing about failure modes such as an unpaid or expired link.

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?

There is a single parameter, session_id, at 0% schema description coverage, and the description never mentions it or clarifies which session it refers to. The name is largely self-explanatory, so the gap is modest, but the description adds no meaning beyond the schema field name.

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 names a specific verb+resource pair: it checks whether the user paid the buy_credits link and credits the balance. It also ties itself explicitly to the sibling tool buy_credits, so the agent can see the relationship between generating the link and confirming payment. It stops short of a one-line statement of what it does not do (e.g., creating the payment link itself).

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?

Usage is implied rather than stated: the reference to the 'buy_credits link' suggests this is called after buy_credits, but there is no explicit when-to-use / when-not-to-use phrasing or mention of polling cadence. An agent can infer the sequence, but the guidance is not spelled out.

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.