Skip to main content
Glama
Sign In

OsmO AI Receptionist

by app.getosmo
OverviewDiscussionsAdmin

Delete a Call Rule

delete_rule
Destructive

Permanently deletes one of the user's screening rules by ruleId. Without confirmed:true nothing is deleted: it returns confirmation_required naming the rule.

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

Input Schema

NameRequiredDescriptionDefault
ruleIdYesA ruleId from list_rules.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes further by disclosing that deletion is permanent and irreversible in effect, and that the no-confirmed path is a non-destructive preview returning a confirmation_required payload naming the rule. That is exactly the behavioral context an agent needs before a destructive call.

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 destructive action and then the safety gate. Every clause earns its place and nothing is repeated.

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 two-parameter destructive tool with no output schema, the description covers what is destroyed, the reversibility, and the shape of the non-confirmed response. It omits any mention of permission or scope requirements, which would round it out.

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 description coverage is 100% and both parameters already carry full explanations, including the confirmed-gate semantics. The description's mention of the confirmed flow adds little beyond the schema, so the baseline 3 applies.

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 description names a specific verb and resource ('Permanently deletes one of the user's screening rules by ruleId') and adds the keying parameter. The word 'deletes' alone separates it from the sibling set's add_rule, update_rule and list_rules without opening any schema.

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?

It clearly describes the two-step usage flow: without confirmed:true nothing is deleted and a confirmation_required preview comes back. What it doesn't do is state when to prefer this over sibling operations (e.g. update_rule to change a rule rather than remove it), so there is clear context but no explicit alternatives or exclusions.

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