Skip to main content
Glama

Time of Meeting

ISO week and US week

week_number
Read-onlyIdempotent

Return only iso_week and us_week for one YYYY-MM-DD date. Use when the user asks for the week number of a date. The response has those two numbers and nothing else: no date, weekday, year, or link. ISO weeks start on Monday, and week 1 contains the year's first Thursday: 2026-12-31 and 2020-12-31 are iso_week 53. The US week starts on Sunday, and 1 January is week 1 of that calendar year, so 2022-01-01 is iso_week 52 and us_week 1. 2027-01-01 is iso_week 53 and us_week 1.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "week_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesCalendar date, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
errorNo
us_weekYes
iso_weekYes
candidatesNo
alternativesNoOther cities that matched the same name, after the best-ranked city was chosen. The order is the site search order: match, then priority, then population.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond that by defining exactly what the response contains and nothing more, and by spelling out the ISO (Monday start, first-Thursday week 1) and US (Sunday start, 1 January is week 1) conventions with worked edge cases.

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?

Front-loaded with what is returned and when to use it, then the ISO/US definitions. The concrete dates (2026-12-31, 2022-01-01, 2027-01-01) earn their place by disambiguating week-53 and year-boundary behavior that an agent would otherwise guess at. Slightly example-heavy, but nothing is wasted.

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?

The tool is trivial to invoke: one fully documented parameter, an output schema, and rich annotations. The description supplies the only thing structured fields cannot — the definitional rules for ISO vs US week numbering at year boundaries. Missing only error behavior for malformed dates, which the schema pattern largely handles.

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 coverage is 100% and the single parameter's pattern (^\d{4}-\d{2}-\d{2}$) and description ('Calendar date, YYYY-MM-DD') already fully specify the input. The description only restates 'one YYYY-MM-DD date' without adding syntax, timezone, or range semantics, so the baseline 3 applies.

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?

States a specific verb and resource ('Return only iso_week and us_week for one YYYY-MM-DD date') and explicitly bounds the output ('no date, weekday, year, or link'). That scope is disjoint from every sibling tool, which do arithmetic, conversions, holidays, or meeting scheduling rather than week-number lookup, so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition: 'Use when the user asks for the week number of a date.' It does not name an alternative or a when-not case, but the tool's narrow purpose makes exclusion unnecessary here.

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