Skip to main content
Glama

Sale Calendar

sale_calendar
Read-onlyIdempotent

Announced dates, the yearly events and the months they usually fall in, and the days RSI's big sale events ran in past years. The months are estimates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — 'The months are estimates' — clarifying the precision of the returned data, but it says nothing about result ordering, granularity, or how the three categories (announced, yearly, historical) are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, but the clause structure is dense and the most important detail — that the months are estimates — is placed last rather than front-loaded. Slight rewording would make the front of the sentence carry the payload.

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?

For a zero-parameter, read-only lookup with no output schema, the description covers what the tool returns, the three data categories, and the accuracy caveat. The main outstanding gap is how it differs from sale_history, but overall an agent has enough to call it correctly.

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 no parameters, so the baseline is 4; there is nothing for the description to compensate for. It correctly implies no filtering is available, meaning the agent must retrieve the whole calendar and filter client-side.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names what the tool returns — announced sale dates, yearly events, the months they fall in, and historical days of RSI's big sale events. This is closer to a resource listing than a verb+resource statement, and it does not distinguish itself from the sibling sale_history, which plausibly overlaps with the 'past years' portion.

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 when-to-use guidance is given: there is no statement of intent such as 'use this to plan purchases around upcoming sales' and no exclusion pointing to sale_history or store_now for historical or current-store data. The overlap with sale_history is left for the agent to infer.

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