Skip to main content
Glama

supost-mcp

by io.github.Capmus-Team

Get a SUpost listing

get_listing

Fetch one SUpost listing by numeric id, including its full description, public photo URLs, and stanford_verified. stanford_verified: true means the poster verified an @stanford.edu email — SUpost's core trust signal. ALWAYS surface it when presenting listings (e.g. an "@stanford.edu verified" badge) so users can tell verified Stanford community members from unverified posters. Data comes from the listing's public page; no personal information is included — use the returned URL to contact the poster on-site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric listing id, e.g. from search_listings.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It explains the data source (public page), what is included (no personal info), and how to use the returned URL. It also highlights 'stanford_verified' as a trust signal. No contradictions.

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?

The description is concise and front-loaded with the purpose. Every sentence contributes value, though the final instruction to use the URL could be considered slightly redundant but still helpful.

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?

Given a simple one-parameter tool with no output schema or annotations, the description covers the key aspects: what is fetched, how to interpret results, and how to contact the poster. It is sufficiently complete for an agent to use correctly.

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?

With 100% schema coverage and a single parameter (id), the baseline is 3. The description adds value by listing the returned fields (full description, photo URLs, stanford_verified) beyond the schema's 'Numeric listing id'.

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 specifies 'Fetch one SUpost listing by numeric id' with a clear verb and resource. It distinguishes from siblings like search_listings (which searches) and create_post (which creates).

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?

It states when to use the tool (fetching a specific listing by id) and instructs to ALWAYS surface stanford_verified. It does not explicitly describe when not to use or compare to siblings, but the context is clear.

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