Skip to main content
Glama

get_schedule

Read-only

Read the user's days: calendar events (fixed), planned blocks for tasks and routines (with the planner's reason codes), working hours and free minutes within working hours. Also returns what the last plan run could not fit. Call this before answering questions about the week or proposing changes.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
startDateNoFirst local date, YYYY-MM-DD; default today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real behavioral context beyond them: blocks carry the planner's reason codes, free minutes are computed within working hours, and the response includes what the last plan run could not fit. That last point is a non-obvious trait an agent could not get from annotations. No mention of result size, pagination, or performance characteristics, which keeps it out of the top band.

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

Conciseness5/5

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

Two sentences, zero filler, and the content enumeration comes before the usage instruction so the agent reads scope first and the call condition second. Every clause carries information an agent needs.

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?

With no output schema, the description usefully documents what comes back (events, blocks, reason codes, working hours, free minutes, unscheduled leftovers), which is the main completeness risk for this tool. Read-only annotations cover the safety profile, and the days bound implicitly caps result size. Minor gap: no explanation of how the default 7-day window interacts with startDate.

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?

The schema is only half documented: startDate carries a format/default description, while days has bounds and a default but no prose explanation. The description says 'the user's days' and never ties it to the days parameter, its default of 7, or the 1-14 ceiling, so it adds almost nothing beyond the structured fields. A baseline 3 is warranted since the schema partially covers both parameters.

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 verb ('Read') and a clearly scoped resource ('the user's days'), then enumerates the returned content: fixed calendar events, planned blocks with planner reason codes, working hours, and free minutes. That enumeration implicitly separates it from get_event (raw events) and get_proposal, but no sibling is named explicitly, so differentiation is inferred 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 Guidelines4/5

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

Gives a concrete when-to-use rule: 'Call this before answering questions about the week or proposing changes.' That is an actionable trigger covering both a question-answering and a planning context. It stops short of naming alternatives or stating when-not to use it (e.g., for a single event lookup, use get_event).

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