Skip to main content
Glama

Brazil company

run_br_companies
Read-onlyIdempotent

Get one company from the Brazil registry (CNPJ / Receita Federal) by registration number or registry URL: name, status, registration date, address and legal form. Flat 5 points per successful run.

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": {
      "company": "<company>"
    },
    "name": "run_br_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistration number or registry URL. e.g. 33000167000101

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the cost model ('Flat 5 points per successful run') and enumerates returned fields, but says nothing about auth needs, not-found behavior, or rate limits beyond that.

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?

Two tight sentences, front-loaded with the core lookup description. The pricing sentence is slightly tangential to tool selection but is short and adds cost awareness, so little is wasted.

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?

With no output schema, the description usefully enumerates return fields, and the parameter is fully specified in the schema. It is nearly complete for a read-only single-record lookup, with only edge-case behavior (missing company, identity/auth) left unstated.

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 the single 'company' parameter is already documented with an example. The description restates 'registration number or registry URL' with no extra format detail, so baseline 3 applies since the schema carries the load.

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?

States a specific verb+resource ('Get one company from the Brazil registry') plus the source system (CNPJ / Receita Federal) and the fields returned (name, status, registration date, address, legal form). The singular 'one company' contrasts with the run_br_companies_search sibling, so an agent can distinguish single-entity lookup from search.

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

Usage Guidelines3/5

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

Usage is only implied: the tool fetches a single company by identifier. There is no explicit 'when to use this vs run_br_companies_search' guidance, no prerequisites, and no exclusions, leaving the agent to infer that search should be used for discovery.

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.

Resources