Tlacuilo

salario_minimo

salario_minimo

Read-only

Mexican minimum wage set by CONASAMI: general daily rate and the Northern Border Free Zone rate for a given year, with monthly equivalents. Price: $0.001 USDC per call (x402).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "salario_minimo"
  }
}

Input Schema

Name	Required	Description	Default
`anio`	No	Year (default: current)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful behavioral context beyond that by disclosing the data components returned and the per-call price of $0.001 USDC via x402, though it does not discuss authentication, rate limits, or failure behavior.

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?

The description is two compact sentences. It front-loads the core data description and then appends the pricing note, with no redundant or filler wording.

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 simple one-parameter lookup with no output schema, the description is largely complete: it names the data source, the rates returned, the inclusion of monthly equivalents, and the call cost. It stops short of clarifying salary currency or response structure, which keeps it from being fully complete.

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%, and the single parameter already documents that it is a year string defaulting to the current year. The description says the data is for a given year but adds no syntax, validation, or edge-case meaning beyond what the schema provides.

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 clearly identifies the specific resource: Mexican minimum wage data from CONASAMI, including the general daily rate, Northern Border Free Zone rate, and monthly equivalents. It does not use an explicit retrieval verb, and it does not distinguish this tool from siblings such as banxico, but the domain and returned fields are still unambiguous.

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?

The description states what data the tool provides for a given year but gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer that it is for Mexican minimum wage lookups, but there is no guidance on when to choose it over related economic-data tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tlacuilo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.