Skip to main content
Glama

Dilligence — certidões de empresas

Entrar na lista do monitoramento

join_monitoring_waitlist
Idempotent

Para quem ainda não tem conta e quer falar com a gente sobre monitoramento de uma carteira grande. Com conta, use create_monitor. Coloca o e-mail na lista; só use se o usuário pediu. Funciona sem autenticação.

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": {
      "email": "<email>"
    },
    "name": "join_monitoring_waitlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOpcional: quantos CNPJs e para quê, ex. 300 fornecedores
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: the call works without authentication and should only be made at the user's request. It does not say what happens after signup (confirmation, follow-up, duplicate handling), which is the main remaining gap.

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?

Four short sentences, front-loaded with the audience and action, followed by the alternative and the consent rule. Every sentence carries distinct information and there is no filler.

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 two-parameter, low-complexity signup tool with no output schema, the description covers audience, action, alternative, consent, and auth requirements. Only the post-submission outcome and the purpose of the `note` field are left unspecified.

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?

With only 50% schema description coverage, the description must carry more weight. It conveys the role of email (the value placed on the list) but says nothing about the optional `note` parameter or any format expectations for the email, leaving that half of the schema undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete action ("Coloca o e-mail na lista") for a specific audience (users without an account who want to discuss monitoring a large portfolio). It also names the sibling tool that serves the opposite case ("Com conta, use create_monitor"), so an agent can distinguish the two without inspecting schemas.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition (no account, wants to discuss large-portfolio monitoring), an explicit alternative (create_monitor for users who already have an account), and a consent guardrail ("só use se o usuário pediu"). Nothing about selection is left to inference.

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.