Conciergr Timetable

Change settings

update_settings

Change any of the business's settings; send only the fields to change. Choosing a trial_contact needs its number or address (given here or already saved). 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": "update_settings"
  }
}

Input Schema

Name	Required	Description
`name`	No	The business's name, up to 120 characters.
`country`	No	ISO two-letter code.
`currency`	No	ISO three-letter code.
`tax_label`	No	GST, VAT, Sales tax; null or empty for no tax.
`time_zone`	No	An IANA time zone, e.g. Asia/Singapore or Europe/London.
`level_word`	No	What the business calls a level (Level, Grade, Stage...), up to 20 characters.
`level_first`	No	true (default): the public page asks a family for a level first; false: it shows every class with the level as a filter.
`tax_rate_bp`	No	Tax rate in basis points (900 = 9%), 0 to 5000; null follows Singapore's GST schedule.
`phone_number`	No	For text and call: digits with country code, optional leading +.
`subject_word`	No	What the business calls a subject (Subject, Class, Style...), up to 20 characters.
`contact_email`	No	For email.
`few_places_at`	No	0 to 50.
`trial_contact`	No	How the public page's trial button reaches the business.
`places_display`	No	bands: 'Few places left' at few_places_at or fewer; exact: the number; full_only: only 'Full'.
`whatsapp_number`	No	Digits with country code, optional leading +.
`prices_include_tax`	No	The business's prices already include its tax.
`show_teacher_names`	No	Show teachers' names on the public page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description usefully adds the owner-only authorization requirement and the partial-update contract (omitted fields are left alone), but says nothing about whether sending null clears a value, validation failure behavior, or rate limits on an open-world mutation.

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, front-loaded with the core action and the partial-update rule, then the conditional dependency, then the permission gate. No filler.

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 17-parameter, all-optional mutation with full schema documentation and annotations covering the safety profile, the description supplies the essentials: partial update, owner-only, and the trial_contact dependency. The one meaningful omission is null semantics for the nullable fields, which an agent would need to clear a tax label or contact.

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 coverage is 100%, so the schema already carries per-parameter meaning and enums. The description adds real value on one point — trial_contact needs a corresponding number or address — but leaves the nullable params (tax_label, phone_number, contact_email, whatsapp_number, tax_rate_bp) unexplained as to how to clear them, so it sits at the baseline.

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?

States a specific verb ('Change') plus the resource ('the business's settings'), and the 'send only the fields to change' phrase communicates partial-update scope. It does not explicitly name get_settings as the read counterpart, but the mutation verb makes the distinction obvious against that sibling.

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?

Clear context: send a subset of fields, trial_contact requires a reachable number/address (supplied here or already saved), and the caller must be the owner. No explicit when-not or 'use X instead' routing, which keeps it at 4 rather than 5.

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?