Skip to main content
Glama
Sign In

Conciergr

by com.conciergr
OverviewDiscussionsAdmin

Switch the assistant on

switch_on_assistant

Switch the assistant on (or resume it after a pause): it starts answering every customer at once. New assistants start paused so nothing goes out before the owner has looked it over; switch on only when the person says so.

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

Input Schema

NameRequiredDescriptionDefault
brandNoWhich assistant (its slug from get_overview `brands[].slug`). Leave out when the business has one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false) by disclosing the actual business consequence: the assistant immediately answers every customer, so outbound messages go out. It also explains the default paused state that motivates the caution — exactly the kind of context annotations cannot carry.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action and its effect, then the caution. Minimal waste; the parenthetical '(or resume it after a pause)' earns its place by covering the paused-state case.

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?

A single-parameter state-toggle with annotations and full schema coverage — the description covers the action, its consequence, and the default state. Only idempotency (what happens when the assistant is already on) is unaddressed.

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% and the sole `brand` parameter is fully documented in the schema (slug source, optional when there is one business). The description adds no parameter-level information, which is acceptable at baseline 3 but leaves value on the table.

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+resource (switch the assistant on / resume it after a pause) and the effect (it starts answering every customer at once). This implicitly distinguishes it from the sibling pause_assistant by describing the inverse state transition, though it never names the 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?

Gives a concrete precondition: new assistants start paused and should be switched on only when the owner says so. That is real usage guidance, but it never names pause_assistant or states what to do if the assistant is already on (no explicit alternative/edge-case routing).

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

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