Skip to main content
Glama
Sign In

OsmO AI Receptionist

by app.getosmo
OverviewDiscussionsAdmin

Update Assistant

update_assistant
Destructive

Switches the user's assistant (by ringgId) and/or its language. Without confirmed:true nothing changes: it returns confirmation_required with the exact change.

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_assistant"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
confirmedNotrue means the user has approved the confirmation_required preview returned by an earlier call with the same arguments, and carries it out. Without it nothing changes and that preview is returned.
ringgAgentIdNoA ringgId from get_assistant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral detail beyond them: nothing changes without confirmed:true, and the call returns confirmation_required with the exact change. It does not describe what is lost when the assistant is switched (e.g., prior assistant settings or state), which matters for a destructive operation.

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?

Two short sentences, front-loaded with the action and followed immediately by the safety mechanism. No filler and nothing repeated from the title.

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 three-parameter mutation tool with no output schema, the critical safety contract (preview-then-confirm) is fully explained. The only gap is the post-success result and the consequences of replacing an existing assistant.

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 67%, with confirmed and ringgAgentId already documented in the schema; only language lacks a description. The description adds that the fields are combinable ('and/or'), clarifying that either change can be made independently, which the schema does not state.

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 and resource: switching the user's assistant and/or its language, with ringgId as the key. It is distinguishable from get_assistant, but the name mismatch (description says 'ringgId', the parameter is 'ringgAgentId') creates a small ambiguity an agent must reconcile.

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?

Clearly explains the confirmation workflow: call without confirmed to get a preview, then re-call with confirmed:true to apply it. It does not explicitly say when to use this versus get_assistant or update_settings, but the mutation context is unambiguous.

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

All OsmO AI Receptionist 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