Skip to main content
Glama
Sign In

Conciergr Timetable

by com.conciergr
OverviewDiscussionsAdmin

Merge two levels

merge_levels
Destructive

Fold one level into another (two spellings of the same level): its classes, fees and trial sessions move over and it is removed. Owner 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": {
      "id": "<id>",
      "into": "<into>"
    },
    "name": "merge_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe level to fold away.
intoYesThe level to keep.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description goes beyond them by naming exactly what is migrated (classes, fees, trial sessions), that the source level is deleted, and that the caller must be an owner. It stops short of stating reversibility or how conflicts are resolved.

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?

One dense sentence that front-loads the action, then the consequences, then the permission constraint. No padding.

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 two-parameter, no-output-schema mutation, the description covers the effects, the deletion, and the auth requirement. It lacks return/confirmation info and edge-case behavior, which is the only remaining gap.

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

Parameters4/5

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

Schema coverage is 100% and the schema already defines id as 'fold away' and into as 'keep'; the description reinforces the directional semantics with its 'fold one level into another' framing, adding slight clarity beyond the schema.

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?

States a specific verb and resource ('Fold one level into another') and immediately clarifies the domain intent ('two spellings of the same level'), which distinguishes it from remove_level or save_level without opening a schema.

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?

'Owner only' gives a permission precondition, and 'two spellings of the same level' implies the use case, but there is no explicit when-to-use versus remove_level or merge_subjects, and no when-not-to guidance.

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

All Conciergr Timetable toolsInspect
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