Skip to main content
Glama

Zaca+ Club y Zaca+ Box

club_and_box
Read-onlyIdempotent

Qué incluyen Zaca+ Club (socios con descuentos, prioridad en la ludoteca y promociones anticipadas) y Zaca+ Box (suscripción a cajas sorpresa de juegos), con precios y enlaces para suscribirse. El contenido de la caja del mes solo aparece cuando ya está desvelado; antes no se puede contar.

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": "club_and_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTienda web: "es" = zacatrus.es (por defecto), "fr" = zacatrus.fr. Define idioma, precios y enlaces.

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?

The annotations already declare a safe, idempotent, closed-world read, so the bar is lower. The description nonetheless adds a real behavioral constraint the schema cannot express: the current month's box contents are only returned once they have been revealed, and may otherwise be unavailable. That is genuinely useful conditional-return context, though nothing is said about link validity or update cadence.

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 sentences: the first front-loads what both offerings contain, the second carries the reveal caveat. Nothing is redundant, though the parenthetical lists make the first sentence dense.

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?

This is a simple one-parameter, read-only informational tool with no output schema, so it does not need return-format detail. The description covers both offerings and the one non-obvious behavioral caveat. It would be complete if it also clarified that this is the public offering overview rather than the user's own membership or box status.

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 country enum fully documents its own effect on language, prices and links, so the schema carries the burden. The description's mention of 'precios y enlaces' loosely corroborates the country parameter but adds no format or default detail beyond the schema. 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?

States a specific resource: the two Zaca+ offerings and exactly what each covers (member discounts, ludoteca priority, early promos vs. surprise game boxes), plus that it returns prices and subscription links. It is clear on its own, but it never distinguishes itself from siblings like my_club and my_box, which an agent could easily confuse it with.

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 says what the tool covers but gives no when-to-use guidance, no prerequisites, and no routing to or away from the obviously adjacent siblings (my_club, my_box). Usage has to be inferred from the content list alone.

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