Skip to main content
Glama

cancunhotels

Cancún por mes

cancun_por_mes
Read-only

Clima (normales del SMN 1991-2020), lluvia, temporada alta o baja y sargazo del año más reciente para un mes. Weather, rain, season and sargassum for a month.

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": {
      "mes": "<mes>"
    },
    "name": "cancun_por_mes"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesYesMes: número 1-12 o nombre (enero, april...)
idiomaNoIdioma de la respuesta / response language (default es)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, openWorldHint=false), and the description goes beyond that by disclosing data provenance and vintage: climate figures are SMN 1991-2020 normals while sargassum covers only the most recent year — an important caveat about mixed data ages. It doesn't describe response structure, but with no output schema that is a modest gap against a strong provenance disclosure.

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?

Two short sentences, front-loaded with the data payload, with no filler. The second sentence is a near-verbatim English translation of the first, which serves a bilingual audience but adds no new information.

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 two-parameter read tool with annotations covering the safety profile and no output schema, the description says what data comes back and over what periods. The only notable omission is any hint of response shape or units (e.g. temperature scale, precipitation units).

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 both parameters (mes, idioma) are fully documented in the schema, so the description need only confirm that a month is the required input. It does that but adds no format or edge-case meaning beyond the schema, which is the expected baseline.

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 names the concrete resource set — SMN climate normals 1991-2020, rain, high/low season, and sargassum — scoped 'para un mes'. That is far more specific than the title alone, and 'sargazo del año más reciente' implicitly separates it from a same-day sargassum sibling, though no verb ('obtén/consulta') is stated explicitly.

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?

It never says when to call this instead of a sibling such as sargazo_hoy (today) or a hotel lookup, nor does it state any prerequisites or exclusions. The month scope implies a use case, but no routing guidance is actually written.

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