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.asiaref
TDQS
A3.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses cost ($0.02), paywall via x402, and fallback behavior when no api_key is provided. With no annotations, this provides valuable behavioral context for a read-like operation.
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 sentences, front-loaded with key action and cost, no redundant information. Every word earns its place.
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?
No output schema, so description should clarify what the snapshot contains (e.g., fields, structure). Lacks details on return format or limits, but for a simple one-call tool it is minimally adequate.
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?
Single parameter api_key is described in schema but the description adds value by clarifying it is optional and its role in bypassing the payment explanation. This goes beyond the schema's minimal 'API key' label.
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?
Description clearly states it returns a snapshot of series per country, distinguishing it from siblings like get_series (specific series) and list_series (list without snapshot). The term 'snapshot' is slightly vague but adequate.
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?
No guidance on when to use this tool versus alternatives, such as get_series or get_series_history. The paid nature is mentioned, but no explicit when-not-to-use or trade-offs.
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.1/5.0
Disambiguation5/5
Each tool targets a distinct reference-data query: minimum wage check, income tax computation, VAT breakdown, working days, public holidays, series current/history/snapshot/catalog, and settlement date. There is no overlap; even get_series and get_series_history are explicitly separated as current vs. historical values.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern (check_, compute_, count_, get_, list_). The one outlier is settlement_date, which is a noun phrase rather than verb_noun, but the deviation is minor and does not cause confusion.
Tool Count5/5
With 10 tools, the set is well-scoped for a reference-data server covering tax, labor, calendars, and settlement. Each tool serves a distinct purpose and none feel redundant or unnecessary.
Completeness4/5
The server provides strong coverage: discovery via list_series, current and historical series values, a bulk snapshot, and domain-specific computations for minimum wage, income tax, VAT, working days, holidays, and settlement dates. Minor gaps exist (e.g., no direct tool for social security contributions), but the core reference-data workflows are well supported.