Skip to main content
Glama

Dilligence — certidões de empresas

Criar conta

signup

Cria a conta do usuário com o e-mail dele e 30 créditos grátis (30 certidões). Devolve api_key, mcp_url (URL do conector já com a chave, para o usuário configurar e não perder o acesso) e app_url. Funciona sem autenticação. O usuário recebe um e-mail avisando.

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": {
      "email": "<email>"
    },
    "name": "signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailYes
agent_nameNoSeu nome, ex. Claude

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 only declare the generic profile (not read-only, open-world, not idempotent, not destructive); the description adds real substance: no auth required, an e-mail is dispatched to the user, and the response carries api_key/mcp_url/app_url that must not be lost. The remaining gap is that it never warns that repeated calls are non-idempotent and will create duplicate accounts, nor what happens on an existing e-mail.

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?

Four short sentences, front-loaded with purpose, then return values, then auth requirement, then the side effect. The parenthetical about mcp_url saving the user's access is justified because it changes how the agent should present the result.

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?

For an unauthenticated creation tool with no output schema, the description covers what is created, what is returned, the side-effect e-mail, and the auth requirement. It falls short on failure/duplicate-account behavior and on describing two of the three inputs, which matters for a non-idempotent signup.

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?

Schema description coverage is only 33%, so the description should compensate; instead it only clarifies that `email` is the account identifier. `name` and `agent_name` carry no explanation in either the schema or the description, leaving two of three parameters semantically opaque.

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

Purpose5/5

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

States a specific verb and resource ("Cria a conta do usuário") plus the concrete outcome (30 créditos grátis / 30 certidões), which is distinguishable from siblings like `account` or `create_api_key` without opening any schema.

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 context is only implied by the verb (a user without an account) and by the note that it works without authentication. There is no explicit when-to-use vs. when-not guidance, no mention of what to do if the e-mail is already registered, and no pointer to the follow-up tools (`account`, `create_api_key`) that overlap with it.

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.