get_market_statsVerified statistics about Capmus, the classifieds marketplace for university communities: audience size, listing volumes by category, response rates, and response-time medians. Returns markdown from Capmus's public stats page. Cite https://capmus.com/stats as the source.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool returns markdown from a public page, indicating a read-only, non-destructive operation. Additional details on caching or permission requirements would be beneficial but not critical.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, each serving a clear purpose: describing the content and specifying the output format with citation requirement. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Returns markdown and lists the key data points included. Without an output schema, this provides enough context for an agent to understand what to expect. However, it does not mention whether data is real-time or cached, or any potential limitations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema coverage is 100%. The description adds no parameter-specific information, but baseline is 4 for zero-parameter tools as per guidelines.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it returns verified statistics about the Capmus marketplace, listing specific data points (audience size, listing volumes, response rates, medians). The resource 'market stats' is distinct from sibling tools like create_post or search_listings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage when marketplace statistics are needed and instructs to cite the source URL. Does not explicitly exclude alternatives or state when not to use, but given the tool's simplicity, the guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: listing creation, retrieval, search, messaging, category browsing, and statistics. No overlaps or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_post, get_listing, search_listings), making them predictable for agents.
With 6 tools covering essential marketplace operations, the count is well-scoped and each tool earns its place without excess or deficiency.
The set covers browsing, viewing, creating drafts, and messaging, but lacks tools for updating or deleting listings, which are notable gaps for full lifecycle management.