Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_simples

Read-onlyIdempotent

Brazilian Simples Nacional and SIMEI (MEI) tax regime status by CNPJ (0.0100 USDC / 2 credits).

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": {
      "cnpj": "<cnpj>"
    },
    "name": "grid402_simples"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjYes14-digit Brazilian CNPJ number.
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context by disclosing the cost model (0.0100 USDC / 2 credits), but says nothing about return shape or error behavior when a CNPJ is not found.

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?

A single tight sentence that front-loads the resource and ends with the pricing signal. Nothing is wasted, though it could be marginally clearer by placing the CNPJ key phrase earlier.

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?

There is no output schema, so the description should hint at what 'status' comprises (e.g. regime classification, MEI eligibility). It covers what the tool takes and costs but leaves the returned payload underspecified for a non-trivial domain lookup.

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 100%, so both parameters (cnpj and payment_tx_hash) are already fully documented in the schema. The description only restates that lookup is keyed by CNPJ, adding no format or validation detail beyond the schema, which fits the baseline 3.

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 specific resource and scope: Simples Nacional and SIMEI (MEI) tax regime status looked up by CNPJ. An agent can tell this is a tax-regime lookup rather than a generic company lookup, though it does not explicitly distinguish itself from siblings like grid402_cnpj or grid402_compliance.

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 or when-not-to-use guidance and no named alternative. The agent must infer from the topic alone whether to call this or the related CNPJ/compliance tools, with no prerequisite or exclusion stated.

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.