Skip to main content
Glama
Sign In

Tlacuilo

by io.github.mastercobeos
OverviewDiscussionsAdmin

dias_habiles

dias_habiles
Read-only

Mexican banking business days per the CNBV calendar: whether a date is a business day, the next and previous business day, and a date plus N business days. Price: $0.002 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": "dias_habiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoBusiness days to add, may be negative (default 0)
fechaNoDate YYYY-MM-DD (defaults to today, America/Mexico_City)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=true, so the description carries the rest and does: it names the authoritative data source (CNBV), the default timezone (America/Mexico_City), and an explicit per-call price with the x402 payment scheme. What it omits is how a caller obtains the 'next/previous business day' results from the two parameters, which is the main behavioral ambiguity.

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 front-loaded sentence with no filler; the domain and calendar are stated first and the price last. The four-capability list is dense enough that the reader must re-parse it to see which parts the parameters actually drive.

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 zero-required-parameter read-only tool this is close to adequate, and the pricing and timezone details are genuinely needed context. The gap is that the advertised modes (next day, previous day) have no described mapping onto the inputs, leaving an agent unsure what a call will return in each case.

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 schema already explains that 'dias' may be negative and 'fecha' is YYYY-MM-DD defaulting to today in Mexico City time. The description adds nothing further about either parameter, so the schema is doing all the work and 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?

It names a specific verb domain and resource: Mexican banking business days on the CNBV calendar, and it enumerates four capabilities (day check, next day, previous day, date + N). The purpose is unmistakable, but it doesn't say how the caller selects among those four outputs using only 'fecha' and 'dias', so the capability list reads as broader than the schema can express.

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 contains no when-to-use or when-not-to-use guidance and does not reference any sibling tool or alternative calendar. An agent learns what the tool computes but not when to prefer it (for example, over generic date arithmetic) or what its limits are.

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

All Tlacuilo toolsInspect
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.

Resources