Skip to main content
Glama
Sign In
@fopost/mcp

@fopost/mcp

Official
by fopost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_post

Cancel a scheduled post to prevent its publication. The post remains stored in the system for potential reuse.

Instructions

Cancel a scheduled post. The post stays in the system but will not be published.

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

Input Schema

NameRequiredDescriptionDefault
idYesPost id (uuid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description conveys the key side effect: the post remains in the system but is not published. It does not mention whether the schedule is cleared or if it can be re-scheduled, but the primary behavior is clear.

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 is a single concise sentence that packs the essential information without any filler. It is well-structured and front-loads the action.

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?

The description is complete for the operation's primary purpose. It does not describe the return value, but for a cancel action, an explicit output is rarely needed. Given the simplicity and no output schema, this is adequate.

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?

The sole parameter 'id' is described in the schema as 'Post id (uuid)', which is sufficient for a simple identifier. The tool description adds no further clarification, but given the 100% schema coverage, a baseline score is appropriate.

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 clearly states the action (cancel a scheduled post) and the outcome (stays in system but not published), which distinguishes it from delete_post. The verb 'cancel' is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (when you want to prevent publication without deletion) but does not explicitly contrast it with alternatives like delete_post or edit_post. It would benefit from a note like 'Use this instead of delete_post to keep the post record.'

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

Deploy Server

Other Tools