Schedule Gizmo

List schedule templates

list_templates

Read-onlyIdempotent

Ready-made schedule templates (shift patterns such as Pitman, DuPont and 24/48; staff rotas for restaurants, cafés, retail, dental offices, security and warehouses; year planners; wedding plans; event agendas), each with its Schedule Gizmo text to start from and a page that explains it. Optionally filter by a word such as 'pitman' or 'wedding'.

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

Input Schema

Name	Required	Description	Default
`search`	No	Optional word to filter by, e.g. 'restaurant'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare it a safe, idempotent, non-destructive read confined to a closed catalog. The description adds genuine value beyond that by disclosing what each result contains: the Schedule Gizmo text to start from plus an explanatory page, which matters since there is no output schema.

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?

Two sentences, front-loaded with the core noun phrase, and the filter note is placed after the content summary where it belongs. The long parenthetical catalog of template categories is verbose but does real work for semantic matching.

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 one-parameter read tool with no output schema, the description covers what is listed, what each item contains, and how to narrow results. Nothing essential for correct invocation is missing, though a note about whether the filter matches partial words would close the last gap.

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 'search' parameter is already documented in the schema, including an example. The description reinforces it as optional and supplies additional example keywords, but adds no syntax, matching behavior, or zero-result semantics beyond the schema.

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 opens with a specific verb+resource ('Ready-made schedule templates') and enumerates concrete template families (Pitman, DuPont, 24/48, staff rotas, year planners, wedding plans), making the tool's content unmistakable. It does not explicitly contrast itself with make_schedule or get_format_guide, so the sibling differentiation is implied by the word 'templates' rather than stated.

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 — this is the browsing/discovery entry point for prebuilt templates — and the description explains the optional keyword filter with examples ('pitman', 'wedding'). It never states when to choose this over make_schedule or get_format_guide, so the agent must infer the routing.

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

All Schedule Gizmo 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?