Conciergr Timetable

Stop showing the timetable

take_all_branches_offline

Take every live branch off the public page at once; nothing is deleted. Returns the branch_ids taken off, to put back later with make_branches_live. 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": "take_all_branches_offline"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description adds critical behavioral details beyond the annotations, such as the guarantee that 'nothing is deleted,' that the tool returns the affected 'branch_ids,' and that it is restricted to 'Owner only.' This is highly valuable context for a mutation tool.

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?

The definition is highly concise. Both sentences are dense with actionable information, front-loading the operational details and the reversal/ownership requirements without any extraneous filler.

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

Completeness5/5

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

It is perfectly complete for a zero-parameter mutation tool. It covers scope (all branches), effect (off public page), reversibility (make_branches_live), and authorization (Owner only).

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?

Since this tool accepts no parameters, the baseline score is 4. The description does not need to elaborate on parameter definitions but efficiently explains the result of the operation.

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?

The tool purpose is crystal clear: it takes every live branch off the public page. It successfully distinguishes itself from the singular 'take_branch_offline' sibling by specifying the scope as 'every live branch'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidelines by mentioning the prerequisite 'Owner only' and referencing 'make_branches_live' for the necessary reversal, defining its lifecycle clearly.

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?