Skip to main content
Glama

supost-mcp

by io.github.Capmus-Team

Message a SUpost poster

send_message

Send a message to the poster of an active SUpost listing. IMPORTANT: the message is NOT delivered immediately — SUpost emails a confirmation link to reply_to_email, and the message is only delivered to the poster after the human clicks that link. Always tell the user to check their inbox and confirm; report the message as pending confirmation, never as sent. The poster's reply goes to reply_to_email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesPlain-text message to the poster (1-5000 characters).
post_idYesNumeric listing id, e.g. from search_listings or get_listing.
reply_to_emailYesThe user's own email address. Receives the confirmation link and the poster's reply. Never invent or guess this - ask the user for it.

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses the asynchronous delivery behavior, the need for user confirmation, the fact that replies go to reply_to_email, and warns against inventing the email address. This is exceptional behavioral transparency.

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 concise, front-loaded with the main action, followed by crucial caveats in a clear structure. Every sentence adds value without redundancy.

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?

Despite no output schema, the description thoroughly explains the entire message flow, including the pending confirmation state and where replies go. It fully addresses the tool's complexity and provides complete context for an agent.

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 baseline is 3. The description adds meaningful context: for reply_to_email it warns not to invent or guess, and for post_id it suggests sources like search_listings. This goes beyond the schema's basic descriptions.

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 'Send a message to the poster of an active SUpost listing,' which is a specific verb and resource, and distinguishes it well from sibling tools like create_post and search_listings.

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?

The description explicitly explains that the message is not sent immediately and requires a confirmation link click, instructing the agent to inform the user and report the message as pending. This provides clear usage guidance and constraints.

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

All supost-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: create_post for drafting, get_listing for fetching a single listing, search_listings for browsing, get_market_stats for statistics, list_categories for taxonomy, and send_message for messaging. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_post, get_listing, send_message). No deviations or mixed conventions.

Tool Count5/5

With 6 tools, the server covers core marketplace operations (create, read, search, message, categories, stats) without being too sparse or cluttered. The count is well-scoped for the domain.

Completeness4/5

The tool set covers essential CRUD-like operations (create, read, search) and messaging, stats, and categories. Missing update and delete tools, but the draft-based publishing model reduces the need. Minor gap, but overall well-rounded.

Resources