Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Publish post now

publish_post_now
DestructiveIdempotent

Publish a post to its network immediately after a two-step confirmation, ensuring the public, irreversible action only happens once the user approves it.

Instructions

Publishes a post to its network immediately. Publishing is public and cannot be undone from here. The first call publishes nothing and returns needs_confirmation, will_happen and confirmation; publishing happens only on a second call with that confirmation.

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": {
      "post_id": "<post_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "publish_post_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post's id, from list_posts or get_recording.
account_idNo
confirmationNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that publishing is public and irreversible, and documents the unusual first-call/second-call confirmation protocol including the returned fields (needs_confirmation, will_happen, confirmation). It still does not mention the idempotency_key's behavioral role or what a failed/partial publish looks like.

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?

Three tight sentences, front-loaded with the action and its irreversibility, then the non-obvious two-call protocol. No filler or repetition.

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?

No output schema exists, and the description covers the important early-return payload, so the agent knows the first call is not a failure. The main remaining gap is that the required idempotency_key is never explained for a destructive, open-world mutation.

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 only 25% and idempotency_key has no description anywhere; the description compensates only for the confirmation parameter, whose semantics the schema already covers in detail. post_id and account_id are handled by the schema, so net additional meaning is modest.

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

Purpose4/5

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

States a specific verb and resource ('Publishes a post') plus the timing constraint ('to its network immediately'), which implicitly distinguishes it from a scheduling sibling. It stops short of naming an alternative, but the resource and effect are 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?

Provides concrete procedural guidance for the two-step confirmation handshake, which is the main usage hazard. It does not state when an agent should prefer schedule_post or copy_post_to_network instead, so the alternative-selection guidance is only implied by 'immediately'.

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