Skip to main content
Glama

Mexico Market Entry & Accounting — Costa Contable

List reviewed Costa services

costa_list_services
Read-onlyIdempotent

List published, reviewed Costa Contable services in Spanish or English.

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

Input Schema

NameRequiredDescriptionDefault
localeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world, safe read profile. The description does add real context beyond them: only 'published, reviewed' services are returned, and the locale selects the language of the listing. It says nothing about pagination, result size, or ordering, which is the remaining gap for a listing tool.

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 with no filler; the most important qualifiers ('published, reviewed') appear before the language detail.

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?

An output schema exists and the tool has only one enum parameter, so the description needn't explain returns or inputs in depth. However, for a discovery tool whose main competitor is costa_search_knowledge, the absence of any routing guidance leaves a meaningful gap.

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?

The single parameter is a required enum of 'es' and 'en', already self-documenting in the schema despite 0% description coverage. The phrase 'in Spanish or English' maps those codes to natural languages, adding slight meaning, but no further format or behavior detail is given.

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 gives a specific verb ('List') and a well-qualified resource ('published, reviewed Costa Contable services'), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from siblings like costa_search_knowledge, but the resource scope is distinct enough to infer the boundary.

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 statement of when to use this tool, when not to, or which sibling to prefer for free-text lookup versus enumeration. The agent must infer usage purely from the name and the word 'List'.

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