Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

get_official_plan

Read-only

Retrieve daily details for an official plan by plan reference, with an optional date range up to 92 days and movement data included by default.

Instructions

Read the days for a listed plan_ref. Omit dates for the default range or supply a range of at most 92 days.

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": {
      "plan_ref": "<plan_ref>"
    },
    "name": "get_official_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
plan_refYes
start_dateNo
include_movementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral constraint not present in the schema: the 92-day maximum range and the existence of a default range when dates are omitted. It says nothing about authorization on plan_ref, pagination of days, or how results are ordered.

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 tight sentences, no filler, with the retrieval scope front-loaded and the range constraint immediately after. Nothing could be removed without losing information.

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

Completeness2/5

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

For a four-parameter read tool with no output schema and zero schema description coverage, the definition leaves two parameters effectively undefined, including one that materially alters the response. The 92-day rule is a good addition, but an agent could still call this with a mis-specified plan_ref or an unexpected movement payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden, and it only partially compensates. It explains start_date/end_date as an optional bounded range, but never explains what a plan_ref is or where to get one, and completely omits include_movements, whose default of true likely changes the returned payload.

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?

"Read the days for a listed plan_ref" gives a specific verb (read) and a specific resource (days of an official plan), which is distinguishable from list_official_plans or the upsert_* siblings. It stops short of explicitly naming a sibling, but the resource scope is clear enough to route on.

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?

It gives real usage rules for the date parameters: omit them for the default range, or supply a range of at most 92 days. That tells the agent how to call it but not when to prefer it over list_official_plans or the training/metrics query tools, so guidance is implied rather than complete.

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