Skip to main content
Glama

Dilligence — certidões de empresas

Definir responsável

assign_item
Idempotent

Define o responsável por um item: "me", o id de um membro (u:...), ou o e-mail de alguém de fora com owner_name (recebe link de envio; e-mail só com send_email=true).

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": {
      "diligence_id": "<diligence_id>",
      "item_id": "<item_id>",
      "owner": "<owner>"
    },
    "name": "assign_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes"me", o id de um membro (u:...) ou o e-mail de alguém de fora (com owner_name; recebe link de envio). Vazio tira o responsável.
item_idYes
owner_nameNoNome de quem é de fora
send_emailNoManda o link por e-mail (só se o usuário pediu)
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / owner / description
      Added value: +"\"me\", o id de um membro (u:...) ou o e-mail de alguém de fora (com owner_name; recebe link de envio). Vazio tira o responsável."
    • addedInput schema / properties / owner / type
      Added value: +"string"
    • addedInput schema / properties / owner_name
      Added value: +{
      +  "description": "Nome de quem é de fora",
      +  "type": "string"
      +}
    • addedInput schema / properties / send_email
      Added value: +{
      +  "description": "Manda o link por e-mail (só se o usuário pediu)",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / owner / description
      Removed value: -"\"me\", o id de um membro (u:...) ou o e-mail de alguém de fora (com owner_name; recebe link de envio). Vazio tira o responsável."
    • removedInput schema / properties / owner / type
      Removed value: -"string"
    • removedInput schema / properties / owner_name
      Removed value: -{
      -  "description": "Nome de quem é de fora",
      -  "type": "string"
      -}
    • removedInput schema / properties / send_email
      Removed value: -{
      -  "description": "Manda o link por e-mail (só se o usuário pediu)",
      -  "type": "boolean"
      -}
  3. Changed4 schema fields changed
    • addedInput schema / properties / owner / description
      Added value: +"\"me\", o id de um membro (u:...) ou o e-mail de alguém de fora (com owner_name; recebe link de envio). Vazio tira o responsável."
    • addedInput schema / properties / owner / type
      Added value: +"string"
    • addedInput schema / properties / owner_name
      Added value: +{
      +  "description": "Nome de quem é de fora",
      +  "type": "string"
      +}
    • addedInput schema / properties / send_email
      Added value: +{
      +  "description": "Manda o link por e-mail (só se o usuário pediu)",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a non-readonly, idempotent, open-world mutation. Beyond that, the description discloses the concrete side effect that an external assignee 'recebe link de envio', which the annotations do not convey and which matters for an outward-facing action. It stops short of describing permission requirements or what happens to a previously assigned owner.

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?

One front-loaded sentence: verb+resource first, then the accepted value forms with their constraints. No filler, and the most error-prone part (owner formats) is placed earliest.

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 5-parameter mutation with no output schema and 60% schema coverage, the description covers the genuinely ambiguous parameter and the e-mail side effect. It leaves the two required identifiers and the reassignment/replacement semantics unexplained, so it is adequate but not fully self-contained.

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?

Schema coverage is only 60%; item_id and diligence_id carry no description in either schema or description. The description does add meaning for the owner format and its coupling with owner_name/send_email beyond the schema's own wording, but does not compensate for the undocumented required identifiers.

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 ('Define o responsável') and resource ('por um item'), then enumerates the three accepted owner forms ('me', 'u:...', external e-mail). An agent can tell this apart from siblings like remove_item or get_item, although no sibling is named explicitly.

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?

Gives conditional usage for the tricky path: external e-mail only works with owner_name and 'só com send_email=true'. However, it never says when to use this tool versus alternatives (e.g. invite_member for outsiders already in the workspace) or any prerequisites/permission context.

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.