Skip to main content
Glama
Sign In

Suara

by com.trysuara
OverviewDiscussionsAdmin

Cancel a booked post

cancel_post
DestructiveIdempotent

Use this when the signed-in owner wants a scheduled post not to go out. First call it without confirm: it says what would be cancelled and changes nothing. Show that to the owner, and call again with confirm true only after they say yes. The post stays approved, so it can be booked again with reschedule_post. A post that's already posted can't be taken down from here.

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": {
      "postId": "<postId>"
    },
    "name": "cancel_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post to cancel
confirmNoTrue only after the owner saw what will be cancelled and said yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark it non-readonly, destructive, idempotent, and open-world, but the description adds the critical two-step behavior: calling without confirm changes nothing and reports what would be cancelled, while confirm true commits. It also states the post remains approved and rebookable, which is not conveyed by annotations.

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?

Four short sentences, front-loaded with the trigger and confirm sequence; each sentence carries distinct information (preview, commit, rebook, limit). No repetitive or filler wording.

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?

Given the two parameters, full schema coverage, no output schema, and annotations covering safety, the description supplies everything needed: trigger, dry-run/commit semantics, post-state outcome, and a hard limitation. Nothing material is missing for correct invocation.

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 100%, so the baseline is 3; however the description adds operational meaning to confirm by explaining that omitting it is a no-change preview and that it should be set true only after the owner approves. postId is straightforward and already documented.

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?

States a specific verb and resource ('cancel' a 'scheduled post') and scopes it to the signed-in owner's booked post. It explicitly distinguishes this from reschedule_post and says already-posted posts cannot be taken down here.

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?

Provides explicit when-to-use ('signed-in owner wants a scheduled post not to go out'), a when-not ('already posted can't be taken down'), and the alternative ('reschedule_post' to book again). It also gives the exact confirm workflow, so the agent knows the first call is a preview and the second is the actual cancellation.

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

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