Skip to main content
Glama
Sign In

Suara

by com.trysuara
OverviewDiscussionsAdmin

Ask for a change to a post

request_post_change
Idempotent

Use this when the signed-in owner wants something changed on ONE specific post they've seen: different words, another photo, a colour, a price or date to fix. Give its postId and the change in the owner's own words, complete. It goes to their Suara assistant or designer, who makes the change and sends the post back to review; nothing changes or posts right away. For anything not about one post, use send_to_suara.

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>",
      "change": "<change>"
    },
    "name": "request_post_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYesExactly what the owner wants changed, in their words
postIdYesThe post to change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent, non-open-world write. The description adds real workflow context beyond that: the request goes to a Suara assistant or designer, who makes the change and returns the post for review, and nothing changes or posts immediately. It stops short of stating permission requirements or what the owner sees on failure, so a 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the when-to-use condition, followed by parameters and then the downstream behavior. Nothing is redundant, though the middle sentence is slightly compressed and reads awkwardly where it ends with "complete."

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?

With only two required parameters, full schema coverage, no output schema, and annotations covering the safety profile, the description supplies everything else an agent needs: trigger, exclusions, the alternative tool, and the fact that the change is staged for review rather than applied immediately.

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 defines both parameters. The description adds only modest meaning: the change must be in the owner's own words and must be complete, which signals to pass a full instruction rather than a terse fragment.

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 ("ask for a change to a post") and scopes it to exactly one post the owner has seen. It explicitly distinguishes itself from the sibling send_to_suara for anything not about a single post.

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 states the trigger (signed-in owner wants something changed on one specific post), gives examples of change types, and names the alternative tool plus the condition that selects it. No inference is required to route between this and send_to_suara.

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