Skip to main content
Glama

Dilligence — certidões de empresas

Criar chave de API

create_api_key

Cria outra chave de API (para outro agente ou sistema). A chave aparece só nesta resposta.

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": {
      "label": "<label>"
    },
    "name": "create_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write profile is covered. The description adds genuinely new behavior: the secret is shown only once in this response and never again, which is critical operational context not present in the schema or annotations. It does not mention auth requirements or scopes, so not a 5.

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, front-loaded with the action and immediately followed by the one-time visibility warning. No wasted wording.

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 simple one-parameter creation tool, the description covers the essential danger (key shown once) and its purpose. However, it omits label semantics and any note on resulting permissions or scope of the created key, which an agent would need to call it confidently with no output schema available.

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 coverage is 0% for the single `label` parameter, so the description carries full burden, yet it says nothing about what a label is, whether it must be unique, or its format constraints. With one required undocumented param, this is a clear gap.

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?

States a specific verb and resource ("Cria outra chave de API") and clarifies the intended recipient ("para outro agente ou sistema"), which distinguishes it from sibling revoke_api_key. It does not explicitly name the sibling alternative, keeping it short of a 5.

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?

The parenthetical implies this is for issuing credentials to a separate agent or system, so usage context is inferable, but there is no explicit when-to-use or when-not-to-use guidance relative to revoke_api_key or invite_member.

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.