Skip to main content
Glama

List reconfigurations

list_reconfigurations
Read-only

The RECONFIGURATIONS of a project's rooms in a window: before every occurrence whose layout matters and whose units stand elsewhere — put there by an earlier occurrence ('by'), or where they stand of themselves — one reconfiguration, ending when the occurrence begins ('for') and lasting the sum of its units' 'moveMinutes'. Each has 'steps' (what, from, to), 'checklist' (Markdown, «what, from, to, who»), 'returning' (every unit goes back where it stood before the occurrence that moved it — the return after a rental: as it was / as it is now), the roles it asks for and keeps away and 'people' who may do it, and its place in its week: 'number', 'ceiling', 'overCeiling' (waiting for an administrator's word), 'approved'. 'weeks' counts them per week. Any member may read.

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": {
      "project": "<project>"
    },
    "name": "list_reconfigurations"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWindow end, ISO 8601. Default: a week after the start; at most 400 days.
fromNoWindow start, ISO 8601. Default: yesterday.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuinely non-obvious behavior. It discloses the authorization rule ('Any member may read') and explains derived semantics — that 'overCeiling' means the reconfiguration is 'waiting for an administrator's word' and that 'returning' distinguishes 'as it was / as it is now'.

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

Conciseness2/5

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

The opening is a single sprawling sentence built from em-dashes and nested clauses, so the core purpose ('list them') is buried rather than front-loaded. The field inventory that follows is useful but reads as a run-on glossary rather than structured description.

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 carries the full return-value burden — and it does document each field's meaning, which is substantial for this domain-specific computed entity. What remains missing is comparison guidance against the approval sibling and any result-size or pagination note beyond the 400-day window cap.

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%, so all three parameters including the ISO 8601 defaults and the 400-day cap are already documented in the schema. The description's only nod to parameters is the vague phrase 'in a window', adding no format or constraint detail beyond structured fields — baseline 3 applies.

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 identifies the resource specifically (a project's room reconfigurations within a time window) and even enumerates the returned fields ('steps', 'checklist', 'returning', 'people', 'number', 'ceiling', 'overCeiling', 'approved'). The listing verb is only implicit in the opening noun phrase, and no sibling is named for differentiation, which keeps it out of 5 territory.

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?

There is no statement of when to reach for this tool versus alternatives such as approve_reconfigurations or the calendar-listing siblings. The only usage context given is access control ('Any member may read'), which is permissioning, not selection guidance.

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