Skip to main content
Glama

Zarok day plan

zarok_get_plan
Read-onlyIdempotent

Use it when the user asks to check or show their Zarok plan, day, tasks or schedule, for example “check my Zarok” or “what do I have today”. Returns the tasks, events, course steps and meals for one date (YYYY-MM-DD) with stable item keys, the plan revision and per-item flags: editable, canRemoveForDay and canMark. Course steps and meals can be marked done. canWrite tells whether this connection may change the plan. Call it before zarok_apply_changes: changes need the item keys and the revision it returns. Clients that support MCP Apps show the day as a card with check boxes. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
dateYesA calendar date in the user’s local time, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / date / description
      Added value: +"A calendar date in the user’s local time, YYYY-MM-DD"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, so the description does not need to carry the full safety burden. It adds valuable behavioral context: it returns stable item keys, a plan revision, per-item flags, canWrite, and whether clients render an MCP Apps card. The final 'Read-only' sentence repeats the annotation rather than adding new information, but the rest of the description meaningfully expands on behavior.

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 description is front-loaded with the usage trigger and core return content, then moves logically into dependencies, flags, and client behavior. It is somewhat dense but each sentence serves a purpose except for the final 'Read-only' statement, which duplicates the annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return values. It does so thoroughly by naming the returned sections, stable item keys, revision, and per-item flags, and by clarifying how the result feeds into zarok_apply_changes. For a read-only single-parameter tool with rich return semantics, this is complete.

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 description coverage is 100%, and the schema already documents the single date parameter with its YYYY-MM-DD pattern. The description restates that it applies to one date but does not add syntax, timezone, or validation detail beyond the schema. The baseline of 3 is appropriate when the schema handles parameter semantics.

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?

The description states a specific verb and resource: retrieving the user's Zarok plan for one date, including tasks, events, course steps, and meals. It distinguishes this from sibling tools by explicitly naming zarok_apply_changes and explaining that this tool must be called first. An agent can identify the tool's purpose without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit usage triggers such as 'check my Zarok' or 'what do I have today', and identifies the prerequisite relationship with zarok_apply_changes. This goes beyond generic guidance by connecting the tool to a concrete workflow and naming the downstream tool that depends on its output.

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