Skip to main content
Glama

Dilligence — certidões de empresas

Convidar membro

invite_member

Convida alguém para o workspace (vê e edita todas as diligências). Envia e-mail de convite: só use 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": {
      "email": "<email>"
    },
    "name": "invite_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new behavior: an invitation e-mail is sent and the invitee receives view-and-edit rights over all diligences, which is the consequence an agent most needs to weigh before calling.

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 consequence, then the usage caution. Nothing is redundant and no sentence could be dropped without losing information.

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 a one-parameter tool with no output schema, the description covers the action, its side effect (e-mail), the permission granted, and a usage restriction. It omits edge-case behavior such as what happens if the address already belongs to a member, which would be the remaining useful detail.

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?

The schema has one required parameter (`email`) with 0% description coverage, so the description must compensate — but it only implies the recipient via "alguém" and gives no format, uniqueness, or existing-member constraints. The parameter is obvious enough that this is a minor gap rather than a fatal one.

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 and resource ("Convida alguém para o workspace") and immediately qualifies the scope of the grant ("vê e edita todas as diligências"), so an agent knows this creates a member with full diligence-level edit rights. It is clearly distinct from remove_member, though it does not explicitly name that sibling.

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?

The clause "só use se o usuário pediu" is an explicit usage gate that tells the agent not to invite speculatively — a meaningful exclusion for an outbound-email tool. It stops short of naming alternatives (e.g., re-sharing via `share`) or preconditions such as the invitee already being a 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.