get_snapshot
PAID ($0.02). Snapshot of every series for every country in one call. Pass api_key if you have one; otherwise the response explains how to pay via x402.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | API key |
reference-data
by dev.latamref
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses cost ($0.02) and payment method (x402), but no other behavioral details; annotations absent so description carries full burden.
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?
Two concise sentences conveying cost, scope, and usage hint with no wasted words.
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?
Covers essential aspects for a simple tool with one optional param and no output schema; slight gap on response format but acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Adds value beyond schema by explaining api_key is optional and fallback behavior; schema coverage is 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Snapshot of every series for every country in one call' with specific verb and resource, distinguishing it from series-specific siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides guidance on api_key parameter and payment fallback, but lacks explicit when-to-use or alternatives among siblings.
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.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool targets a distinct operation: compliance check, tax computation, VAT breakdown, day counting, holiday retrieval, series value/history/snapshot, catalog listing, and settlement date calculation. Even where underlying data overlaps (e.g., minimum wage as a series), the outputs and use cases are clearly differentiated.
Naming Consistency4/5
Nine of ten tools follow a clear verb_noun pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). The outlier is settlement_date, which uses a noun phrase rather than a verb-based name, though it remains unambiguous and readable.
Tool Count5/5
With 10 tools, the server is well-scoped for its reference-data purpose, covering tax, wages, holidays, working days, series discovery, and settlement dates. Each tool earns its place without redundancy or bloat.
Completeness5/5
The surface provides comprehensive coverage: discovery via list_series, current/historical data via get_series and get_series_history, a full snapshot, tax computations, wage compliance, public holidays, working day counts, and settlement date calculations. There are no obvious gaps or dead ends for the intended domain.