Skip to main content
Glama
Sign In

Flaghand

by com.flaghand
OverviewDiscussionsAdmin

Schedule a draft on its connected account without passkey approval; immediate posting is refused

schedulePost
Destructive

Schedule a draft on its connected account without passkey approval; immediate posting is refused

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": {
      "draft_id": "<draft_id>",
      "rev": "<rev>"
    },
    "name": "schedulePost"
  }
}

Input Schema

NameRequiredDescriptionDefault
revYesCurrent draft revision from getDraft. A concurrent edit or move is refused.
modeNoschedule only. post_now always returns post_now_forbidden for agents.
post_atNoExact future posting time, with UTC offset. At least one minute ahead. Never now.
draft_idYesDraft ID or stable workspace post number, such as "#38" or "38".
workspaceNoLeave out for the token's workspace (ws_…).
idempotency_keyNoA new UUID per request; resending the same key and request is a safe retry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is carried by structured data. The description adds useful auth context (no passkey approval required) and the post_now refusal, but it does not explain what the destructive side effect is, whether the draft is consumed or mutated, or what preconditions on the connected account must hold.

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?

A single front-loaded sentence with no filler, and the core action plus the two key constraints appear immediately. It is verbatim identical to the title, which is efficient but leaves no room for any additional orientation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, destructive mutation with no output schema, the description covers the action and two constraints but omits prerequisites (connected account must exist/authorize), what success returns, and what happens to the draft afterward. The rich schema compensates for parameter detail, but the behavioral gaps keep this at minimum-viable.

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 the schema itself documents rev staleness, mode's post_now_forbidden behavior, post_at's future/UTC constraints, draft_id formats, workspace omission, and idempotency_key retry semantics. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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?

'immediate posting is refused' gives a concrete when-not condition, telling the agent this is for future-dated scheduling rather than publishing right away. However, it never names the alternative to use when immediate posting is desired (createPost) or how to undo scheduling (unschedulePost), so routing is inferred rather than stated.

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

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