Skip to main content
Glama

iso-week

ISO week calendar. No input: the current ISO 8601 week number and week-numbering year, the Monday-Sunday span of the week, the 52/53-week year shape, the weeks elapsed and remaining, and the ISO day of week, answered fresh on every call. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "iso-week"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses zero-argument operation, fresh computation per call, a per-call price of $0.005 in USDC on Base mainnet via x402, and the exact failure behavior (HTTP 402 with machine-readable payment terms). The main omission is rate limits or latency expectations, but the payment and error contracts are unusually well disclosed.

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?

The purpose and no-input nature are front-loaded, followed by the enumerated return values and then the pricing/payment contract. It is a single dense block with little waste, though the return-value list is long enough that structure (e.g., separating output from cost) would aid scanning.

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?

Given no annotations and no output schema, the description must cover both behavior and return values, and it does list the returned fields plus the payment/HTTP 402 flow. The remaining gap is that it doesn't specify the response format or timezone handling for the week span, which matters slightly for a date tool.

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?

The tool takes zero parameters, which is the baseline-4 case, and the description explicitly confirms this with 'No input', removing ambiguity about whether an argument is expected. Nothing further is required or added.

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 states a concrete resource (ISO week calendar) and enumerates exactly what is returned: ISO week number, week-numbering year, Monday-Sunday span, 52/53-week year shape, weeks elapsed/remaining, and ISO day of week. This is far more specific than a name restatement. It does not, however, explicitly differentiate itself from potentially overlapping siblings such as agent-time, so it stops short of the top score.

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 implied rather than stated: 'No input' plus 'answered fresh on every call' tells the agent this is a zero-argument, non-cached lookup for the current week. There is no explicit when-to-use or when-not clause and no named alternative for related date/iCalendar needs, leaving routing to inference.

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