Skip to main content
Glama

Dilligence — certidões de empresas

Ver conta e saldo

account
Read-onlyIdempotent

Conta atual: saldo em créditos (1 crédito = 1 certidão emitida), membros, chaves, extrato e pagamento (pacotes, cartão salvo).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the contents of the response (balance, members, keys, statement, payment methods) and the credit conversion rule (1 credit = 1 issued certificate), which an agent cannot get from the annotations. It does not describe formatting or whether secrets/keys are masked, which is the main remaining gap.

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?

A single compact sentence with no filler, front-loaded with the resource ('Conta atual'). The colon-separated enumeration is dense and readable, though it reads as a feature list rather than a statement of what the tool does, which slightly weakens the lead.

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 parameters, no output schema, and annotations covering the safety profile, the description's main burden is telling the agent what comes back, and it does that by enumerating the five data areas. The gaps are minor: no note on auth requirements or whether any part of the payload (e.g., keys) is redacted.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical about the credit-to-certificate ratio adds useful semantic grounding for interpreting the balance value returned.

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 the resource (current account) and enumerates exactly what the tool exposes: credit balance, members, API keys, statement, and payment info. It is specific enough to distinguish it from sibling write tools like buy_credits or create_api_key, though it is a noun list rather than a verb phrase, so the action (view/read) is only implied.

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: an agent can infer this is the place to look when it needs account-level state (balance, members, keys, payment). There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as list_diligences or check_payment for narrower queries.

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.