Skip to main content
Glama

Colombia company

run_co_companies
Read-onlyIdempotent

Get one company from the Colombia registry (RUES, Registro Mercantil) by NIT or registry URL: name, status, registration date, address, legal form, economic activity, legal representation and establishments. 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_co_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesNIT or registry URL. e.g. 899999068-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/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 two things annotations cannot: the upstream data source (RUES/Registro Mercantil) and the cost model ('flat 5 points per successful run'), which is genuinely useful for an agent budgeting calls. It stops short of disclosing failure behavior or whether a URL and a NIT for the same company yield identical results.

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?

One front-loaded sentence carries purpose, source, keying method and the field inventory, followed by a short cost note. Nothing is redundant and nothing is buried; with no output schema present, the field enumeration is load-bearing rather than 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 one-parameter read tool with no output schema, the description compensates well by naming the registry and listing the fields returned, so the agent knows what to expect. Gaps remain around miss/error behavior and the exact JSON shape, but these are minor given the tool's simplicity and the annotations covering side effects.

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% with a single documented parameter including an example (899999068-1), so the schema does the heavy lifting. The description's 'by NIT or registry URL' mirrors the schema rather than extending it — it does not explain URL format, check-digit handling, or whether bare digits are acceptable. Baseline 3 is correct.

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 and resource — fetch ONE Colombia company from the RUES/Registro Mercantil registry — and specifies the two accepted identifiers (NIT or registry URL). Enumerating the returned fields (name, status, registration date, address, legal form, economic activity, legal representation, establishments) makes the scope unambiguous versus the sibling run_co_companies_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?

Use case is implied: a single-record lookup keyed by NIT/URL, contrasted with the *_search sibling that takes free-text queries. However, the description never states when to prefer this over run_co_companies_search, nor what happens if the identifier is unknown or the company is not found. No explicit exclusions or prerequisites.

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