Vaper Club Agent

search_posts

Read-onlyIdempotent

Search published Vaper.club posts by keyword (brand, model, topic). Returns paged post summaries with source URLs. Date filters apply to the returned page only.

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": {
      "query": "<query>"
    },
    "name": "search_posts"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`type`	No	Optional content type: article or video.
`query`	Yes	Search keywords. Required.
`sort_by`	No	relevance (default) or latest.
`category`	No	Optional post category code.
`end_date`	No	Optional end date (ISO 8601).
`language`	No	Optional language code such as en or de.
`page_size`	No	Page size, 1-20. Default 10.
`start_date`	No	Optional start date (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only cover read-only and idempotent hints, but the description adds real behavioral context: results are paged summaries with source URLs, and date filters apply to the returned page rather than the whole result set. That last caveat is a non-obvious trait that prevents misuse. It stops short of stating ranking or total-count behavior.

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 short sentences, zero filler, with the core purpose front-loaded and the date-filter caveat placed where it will be read before calling. Every sentence carries information.

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?

With nine parameters and no output schema, the description does enough: it names the return shape (paged post summaries with source URLs) and flags the date-filter caveat. Coverage of sorting, paging limits, and language behavior is left to a fully documented schema.

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 100%, so the baseline is 3. The description does reinforce that query matches brand/model/topic and clarifies the scope of start_date/end_date, but leaves sort_by, category, language, and page sizing entirely to the schema.

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 ('Search published Vaper.club posts by keyword') and narrows keyword scope to brand, model, or topic. It is clearly distinguishable from siblings like search_brands or search_products by resource, though it never names an alternative explicitly.

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?

Usage is implied by 'search published posts by keyword' but there is no explicit guidance on when to use this versus get_latest_posts for browsing or the other search_* tools for brands/products/shops. The agent must infer the boundary.

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

All Vaper Club Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?