Skip to main content
Glama
Sign In

VanAuto Campers

by pl.vanauto
OverviewDiscussionsAdmin

Search wanted ads

search_wanted_ads
Read-onlyIdempotent

Search marketplace wanted ads (kupię / poszukuję) posted by buyers looking for camper parts and accessories. Supports text, category and subcategory filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_wanted_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based).
queryNoFree-text search over title, description, manufacturer and part number.
perPageNoRows per page (1-50).
categoryNoCategory slug, e.g. "appliances", "plumbing_water".
subcategoryNoSubcategory slug, e.g. "toilets", "refrigeration".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds the available filter dimensions but says nothing extra about pagination limits, result ordering, or freshness of these ads.

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?

Two tight sentences: purpose first, supported filters second. Zero filler and nothing that could be cut.

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?

For a 5-parameter, all-optional, read-only search with no output schema and full schema coverage, the description supplies what is needed to invoke it correctly. A brief note on result shape or paging behavior would make it complete.

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% — every parameter (page, query, perPage, category, subcategory) is documented in the schema, including slugs and defaults. The description only restates the filter categories, adding no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource: 'Search marketplace wanted ads ... posted by buyers looking for camper parts'. The domain gloss (kupię / poszukuję) and the buyer-side framing distinguish it from listing-search siblings, though no sibling is named.

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 only implied: an agent can infer this is for finding buyer demand rather than seller listings, but the description never states when to prefer it over search_marketplace_listings or search_campers, nor any exclusions.

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

All VanAuto Campers toolsInspect
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