Skip to main content
Glama
Sign In

OsmO AI Receptionist

by app.getosmo
OverviewDiscussionsAdmin

Update a Call Rule

update_rule
Destructive

Changes one of the user's screening rules by ruleId; only the fields passed are changed. Without confirmed:true nothing changes: it returns confirmation_required with the exact change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ruleId": "<ruleId>"
    },
    "name": "update_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe rule as the user would say it, e.g. "Put Mom through".
emojiNoOne emoji shown beside the rule, e.g. "📞".
promptNoThe same rule as an instruction to the call assistant, e.g. "When Mom calls, transfer the call to me."
ruleIdYesA ruleId from list_rules.
isActiveNofalse turns the rule off without deleting it.
mentionsNoEach person the rule is about, with their full number in international form.
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.
expiresAtNoISO 8601; null makes it permanent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes well beyond them: it discloses partial-update semantics ('only the fields passed are changed') and a two-step confirmation protocol where an unconfirmed call is a no-op returning confirmation_required with the exact change. That is precisely the behavioral context an agent needs before invoking a destructive 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?

Two short sentences, zero filler, with the mutation scope front-loaded and the confirmation safety gate immediately after. Nothing is redundant.

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 an 8-parameter destructive mutation with no output schema, the definition covers the essentials: partial-update behavior, the required identifier's source, and the confirmation handshake. Minor gaps remain, such as what happens when ruleId is unknown or when confirmation arguments diverge, but the schema carries those cases.

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 explains confirmed, ruleId, mentions, and expiresAt in detail, and the description mostly reinforces that. It adds the meaningful semantic that omitted fields are left untouched, but contributes no new syntax or format detail beyond the schema.

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 ('Changes one of the user's screening rules by ruleId') plus the key that identifies it, which cleanly separates it from add_rule and delete_rule on verb alone. It does not name a sibling explicitly, so it stops just short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the verb (modify an existing rule rather than create or delete one), and the description adds a real usage rule in the confirmed:true gate. There is no explicit when-not guidance or routing to alternatives such as add_rule for new rules or delete_rule for removal.

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