Skip to main content
Glama

Dilligence — certidões de empresas

Marcar como não se aplica

mark_not_applicable
Idempotent

Marca o item como "não se aplica", com o motivo.

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>",
      "reason": "<reason>"
    },
    "name": "mark_not_applicable"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
item_idYes
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered without the description. The description adds essentially nothing beyond that: it does not say whether the action is reversible, whether the item must be in a particular state, or what permissions/scoping apply to diligence_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero wasted words, which is structurally fine. However, the brevity crosses into under-specification, since the space freed by terseness is not used for any of the missing context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter mutation tool with no output schema and no schema documentation needs the description to carry the load, and this one does not. Nothing is said about the effect on the diligence, the response, or error conditions, so an agent cannot predict the outcome of a call.

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 description coverage is 0% with three required parameters. The description only gestures at one of them via 'com o motivo' (the reason), and says nothing about diligence_id or item_id, their ID formats, or the required relationship between them. It provides partial compensation for the coverage gap but leaves two parameters entirely unilluminated.

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 states a specific verb and effect ('Marca o item como "não se aplica"') plus the accompanying input ('com o motivo'), so an agent knows this sets a not-applicable status on an item. It is clear enough to distinguish from siblings like remove_item or retry_item, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use context, no prerequisites, and no mention of when NOT to use it versus remove_item, retry_item, or get_item. The agent must infer the trigger condition purely from the phrase 'não se aplica'.

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.