Skip to main content
Glama

Mexico company

run_mx_companies
Read-onlyIdempotent

Get one company notice from the Mexican Registro Público de Comercio publications (PSM) by publication number: company name, legal form, publication type, title and date, a link to the published text and the publication history. 5 points per returned record.

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_mx_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesPublication number. e.g. 2026-0000001606

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description's job is lighter. It adds two genuinely useful facts not in the annotations: it returns exactly one notice, and it costs '5 points per returned record', which lets an agent weigh spend before calling.

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 sentence, front-loaded with the verb and resource, followed by the output field list and the cost note. Every clause carries information; the field enumeration is long but pays for itself because there is no output schema.

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?

For a one-parameter lookup with no output schema, listing the returned fields is the right call and is done. What is missing is the relationship to neighbors in a 200+ tool catalog — how an agent obtains a publication number and when to prefer run_mx_companies_search or run_mx_company_publications instead.

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 coverage is 100% and the schema already says 'Publication number. e.g. 2026-0000001606'. The description's 'by publication number' reinforces the semantic but adds no format, provenance, or error-handling detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Get one company notice from the Mexican Registro Público de Comercio publications (PSM) by publication number') and enumerates the returned fields, so an agent knows exactly what comes back. It does not, however, differentiate itself from the similarly named siblings run_mx_companies_search and run_mx_company_publications, leaving ambiguity about which one to call.

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?

The phrase 'by publication number' implies the precondition (you must already hold a PSM publication number), which is useful. But there are no explicit when-to-use statements, no exclusions, and no pointer to run_mx_companies_search for discovering a publication number or to run_mx_company_publications, so an agent must infer the routing.

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