Skip to main content
Glama

Dilligence — certidões de empresas

Ver carteira de monitoramento

get_monitor
Read-onlyIdempotent

O painel de uma carteira: cada empresa × certidão (ok, pendencia, buscando, parou, a_buscar, na), validade, próxima renovação, alertas recentes e app_url.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "get_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing the response shape — the status vocabulary (ok, pendencia, buscando, parou, a_buscar, na), validity/renewal fields, and app_url — which is important context given there is no output schema. It stops short of describing size limits or how statuses are computed.

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

Conciseness4/5

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

One compact sentence, front-loaded with the subject and then the field list. Efficient, though the noun-fragment style without a verb slightly reduces clarity for an agent scanning for actions.

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?

With no output schema, the description usefully enumerates the returned fields, which covers the main completeness burden. However, it leaves the required monitor_id undocumented and says nothing about failure modes (invalid monitor_id, empty portfolio), so an agent lacks enough to call it confidently in edge cases.

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?

The single parameter monitor_id has 0% schema description coverage and the description never explains it; only the loose phrase 'de uma carteira' hints that it identifies a monitoring portfolio. With low coverage and a required identifier, the description should have compensated but does not.

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 the resource ('o painel de uma carteira') and enumerates exactly what the payload contains: per company × certificate statuses, validity, next renewal, recent alerts, and app_url. That gives a clear picture of the returned artifact, though it never uses an explicit retrieve verb and does not distinguish itself from siblings such as get_diligence or get_item.

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 guidance on when to call this versus list_monitors or get_item, and no prerequisites (e.g., that a valid monitor_id from list_monitors is required). The agent must infer usage from the sibling names alone.

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.