Skip to main content
Glama

Dilligence — certidões de empresas

Ligar link de leitura

share
Idempotent

Liga ou desliga o link de leitura da diligência (quem tiver o link vê os itens e baixa os PDFs, sem login).

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>",
      "enabled": "<enabled>"
    },
    "name": "share"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only say this is a non-read-only, non-destructive, idempotent, open-world mutation; the description adds the security-relevant fact that enabling exposes items and PDFs to anyone holding the link without login. That is meaningful context beyond the annotations. Gaps remain: it doesn't say whether the link URL is returned, whether disabling invalidates previously distributed links, or what permissions are required.

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?

A single front-loaded sentence with the state-change verb first and the explanatory parenthetical second. Every clause carries information; nothing is redundant.

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 two-parameter toggle with no output schema, the description covers the important "what enabling does" angle, which is the main risk. It is still incomplete on the disable path, on whether a shareable URL is produced (no output schema exists to answer that), and on authorization requirements.

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 0%, so the description must carry the parameter meaning. It does so only implicitly: "da diligência" maps to diligence_id and "liga ou desliga" maps to enabled, but neither parameter is named and there is no detail on the expected ID format. It compensates partially, matching the low-coverage baseline rather than exceeding it.

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 pair ("liga ou desliga") and resource ("link de leitura da diligência"), and the parenthetical explains the concrete effect: anonymous viewers can see items and download PDFs. The name "share" is generic on its own, but the description removes that ambiguity. It does not explicitly contrast with siblings like invite_member, but none is a close substitute, so differentiation is implicit.

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 inferable from the toggle semantics: use it to grant or revoke anonymous read access to a diligence. However, there is no guidance on prerequisites (owner/admin permission needed?), no when-not-to-use (e.g., instead of invite_member when you want authenticated, tracked collaborators), and no statement of consequences for revoking.

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.