MoneyTools x402 agent toolkit

Public holidays (US federal)

public_holidays

Read-onlyIdempotent

US federal holidays with observed dates, plus the next holiday. The Taiwan calendar is no longer offered (HTTP 410 if country=TW). Free: 10 calls/day; then $0.001/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

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

Input Schema

Name	Required	Description	Default
`year`	No	year
`country`	No	US (default). TW is retired and returns 410.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- changedInput schema / properties / country / description
```
Previous value: -"TW | US"New value: +"US (default). TW is retired and returns 410."
```
- changedInput schema / properties / country / examples
```
Previous value: -[
-  "TW"
-]New value: +[
+  "US"
+]
```
AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and open-world traits, but the description adds substantive context beyond them: 10 free calls/day, $0.001/call thereafter, the two payment paths (x402 via _meta or X-API-Key credits), and the HTTP 410 for country=TW. That is real operational information an agent needs before calling.

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?

Three short sentences, front-loaded with the capability before pricing and the hosting tag. The pricing detail earns its place given the pay-per-call model; the '[served by tools.moneytools.dev]' suffix is the only filler.

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?

An output schema exists so return values need no explanation, and the description covers the error case and billing model. Little an agent needs is missing for a two-optional-parameter read tool.

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 both parameters already document year and country defaults, including the TW 410. The description largely restates the schema's country note; baseline 3 is appropriate.

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 and scope: 'US federal holidays with observed dates, plus the next holiday.' An agent can tell exactly what it returns. It doesn't explicitly contrast with the sibling business_days, so it stops short of a 5.

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?

Usage is only implied by the scope statement; there is no explicit when-to-use or when-not-to-use guidance versus alternatives such as business_days. The TW retirement note is a constraint, not routing guidance.

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

All MoneyTools x402 agent toolkit tools Inspect

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

Need Help?