Skip to main content
Glama

Dilligence — certidões de empresas

Ver carteiras de monitoramento

list_monitors
Read-onlyIdempotent

Carteiras de monitoramento do workspace, com quantas empresas têm pendência e a próxima renovação.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered structurally. The description adds genuine content beyond that — it discloses that each portfolio entry surfaces a pending-company count and the next renewal date. It stops short of describing ordering, whether empty portfolios are included, or how the counts 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 short sentence with the resource front-loaded and the two return highlights appended; nothing is redundant. It is a noun phrase without an explicit verb, which costs a little immediacy but wastes no space.

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 simple, parameterless, read-only list tool with no output schema, the description supplies exactly the missing piece — what each returned item contains. An agent has enough to call it correctly; only ordering/volume behavior is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the description correctly does not invent any, so there is nothing to mis-specify. Baseline 4 applies for a no-parameter tool with a fully covered (empty) schema.

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 concrete resource — workspace monitoring portfolios ('carteiras de monitoramento do workspace') — and adds the two payload highlights (companies with pending items, next renewal). Combined with the name list_monitors, an agent can tell this apart from singular/detail siblings such as get_monitor, create_monitor or add_monitor_companies, though the description itself never draws that contrast.

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 explicit when-to-use guidance: nothing says to call this for an overview versus get_monitor for a single portfolio, or that this is the entry point before add_monitor_companies. The only implicit signal is the workspace scoping ('do workspace'), which is weak routing guidance for an agent choosing among 30+ siblings.

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.