Conciergr Timetable

Add or change one fee

save_fee

Add a fee, or change one (give its id; send only the fields to change). A second fee for the same thing in overlapping months is refused. Owner only.

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

Input Schema

Name	Required	Description
`id`	No	The fee to change; leave out to add one (then name, category, charged, per, first_month and last_month are needed).
`per`	No
`mode`	No
`name`	No	What the business calls it, up to 120 characters.
`note`	No	Up to 200 characters.
`charged`	No	ongoing: every period while enrolled; on_enrolment: once on joining; when_used: each time it is used.
`lessons`	No	Lessons the amount buys.
`category`	No
`class_id`	No	Narrow it to one class.
`currency`	No	3-letter code; defaults to the business's currency.
`prorated`	No	Charged in part for a part period.
`confirmed`	No	false marks a price still to confirm with the business.
`level_ids`	No	Narrow to these levels; empty means every level.
`branch_ids`	No	Narrow to these branches; empty means every branch.
`last_month`	No	In force until YYYY-MM.
`amount_rule`	No	fixed (needs amount_cents), free, one_period_fee (equal to one period's tuition), ask (ask the branch), tbc.
`first_month`	No	In force from YYYY-MM.
`nth_subject`	No	This price is for the 1st, 2nd... subject a child takes.
`subject_ids`	No	Narrow to these subjects; empty means every subject.
`amount_cents`	No	The amount in cents, as the business states it (with or without tax: see includes_gst).
`includes_gst`	No	The amount already includes the business's tax.
`period_label`	No	e.g. Term 3.
`days_per_week`	No	Days a week this price covers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) the description discloses the overlap uniqueness rule ('a second fee for the same thing in overlapping months is refused') and the authorization requirement ('Owner only') — both are operationally important and not available in structured fields. It does not say what happens on success (returned id) or whether omitted fields are preserved on edit.

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?

Three short sentences, zero filler, with the add-vs-change distinction and the patch instruction front-loaded before the constraint and permission notes.

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 23-parameter mutation with no output schema, the description covers mode selection, partial-update semantics, the uniqueness constraint, and who can call it. The main remaining gap is the return value, which matters here because a caller creating a fee likely needs the new id.

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 87% and the enums document themselves, so the schema carries most of the semantic load. The description's only added value is the conditional creation requirement (name, category, charged, per, first_month, last_month), which is already stated in the id parameter's own description.

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 names the resource (fee) and both operations precisely: create when no id, edit when an id is supplied. It lets an agent distinguish this from sibling mutators like remove_fee or read paths like get_fee/query_fees indirectly, but it never names those siblings explicitly.

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?

'give its id; send only the fields to change' gives concrete instructions for both modes and clarifies that updates are partial rather than full-replacement. It does not name an alternative tool (e.g. query_fees to find an id, get_fee to inspect before editing), so the when-to-use is clear but the routing guidance is incomplete.

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

All Conciergr Timetable tools Inspect

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

Need Help?