Skip to main content
Glama

Mexico Market Entry & Accounting — Costa Contable

Compare Mexican company forms

costa_compare_entities
Read-onlyIdempotent

Return reviewed educational comparison data for S.A., S. de R.L. and SAS when available; does not determine eligibility or recommend an entity.

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": {
      "locale": "<locale>"
    },
    "name": "costa_compare_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeYes
entitiesNo

Output Schema

NameRequiredDescriptionDefault
warningYes
entitiesYes
educational_dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still adds real value beyond them: 'reviewed educational' signals curated, non-authoritative content and 'when available' warns that output may be partial for some entity forms — a caveat an agent would otherwise miss. It stops short of saying what the response looks like or whether missing data is omitted or flagged.

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?

A single sentence with the payload front-loaded and no filler; the caveat and the disclaimer each earn their place. Nothing is repeated from the schema or annotations.

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?

An output schema exists and annotations cover safety, so return-format explanation is unnecessary. For a two-parameter read-only tool the description is nearly sufficient; the only meaningful gap is the unmentioned required locale selector and the two-entity minimum, which an agent must discover from the schema.

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 0%, so the description must carry parameter meaning and only partly does: naming 'S.A., S. de R.L. and SAS' effectively explains the entities enum values and implies the tool operates on a set of entity forms. It says nothing about the required locale parameter or the minItems=2/maxItems=3 constraint, though those enums are largely self-explanatory in the schema.

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 (return) and resource (reviewed educational comparison data) scoped to three named Mexican entity forms, and adds a negative boundary ('does not determine eligibility or recommend an entity'). It is distinguishable from the checklist/services/knowledge siblings by its comparison framing, though it never names an alternative explicitly.

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 exclusion clause tells the agent this is not an eligibility or recommendation tool, which is meaningful scope guidance. However, there is no positive trigger ('use when a client asks to compare S.A. vs SRL vs SAS') and no pointer to the sibling tools that would handle eligibility or recommendations, so the when-to-use routing is only implied.

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