Skip to main content
Glama
Sign In

Suara

by com.trysuara
OverviewDiscussionsAdmin

Change when a post goes out

reschedule_post
DestructiveIdempotent

Use this when the signed-in owner wants an approved post to go out at a different time, or to book an approved post that isn't booked yet. Give the time in the business's own timezone. First call it without confirm: it says exactly what would change and changes nothing. Show that to the owner, and call again with confirm true only after they say yes. Only posts the owner already approved; a post that's already posted can't be moved. Each post publishes once per platform.

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>",
      "when": "<when>"
    },
    "name": "reschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenYesThe new time in the business's own timezone as YYYY-MM-DDTHH:MM (e.g. 2026-11-07T19:00), or now
postIdYesThe post to move
confirmNoTrue only after the owner saw what will change 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?

Beyond the annotations, it discloses that the first call changes nothing and returns an exact preview, that publication is impossible to reschedule afterward, and that each post publishes once per platform. The signed-in-owner wording also clarifies the operating context, while the eventual mutation is consistent with the write and destructive hints.

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?

The description front-loads selection criteria, then presents the invocation protocol and constraints in compact, purposeful sentences. There is no filler, and even the final once-per-platform statement contributes distinct behavioral information.

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?

For a flat three-parameter mutation with no output schema, it covers the actor, eligible resource states, timezone, confirmation protocol, preview behavior, and publication constraints. An agent can select and invoke it safely without inferring any critical workflow step.

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, and the timezone and confirm wording partly repeat the schema. The description nevertheless adds important operational semantics for confirm: omitting it produces a non-mutating preview, and the second invocation applies the change only after that preview has been shown and accepted.

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 opening sentence identifies the actor, resource, preconditions, and both supported operations: moving an approved post to a different time and booking an approved post that is not yet booked. This clearly distinguishes it from siblings such as approve_post, cancel_post, and request_post_change.

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?

It gives explicit usage conditions and exclusions: the post must already be owner-approved, and an already-posted item cannot be moved. It also prescribes the complete two-call workflow, requiring a preview without confirm, owner review, and a second call with confirm true only after affirmative consent.

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