Partle

search_wanted

Read-only

Browse public buy requests — what users are looking to buy but haven't found through normal supply.

The demand side of Partle. Use this when an agent wants to **offer
matches** (cross-reference open requests against `search_products`
and surface hits) or just survey unmet demand. Every result is a
public posting — users put these up specifically so suppliers can
reach them.

Buy requests are independent of personal inventory (which is private):
these are sales-facing ads, not workshop tracking notes.

Read-only. No authentication. Rate-limited 100 req/hour per IP.

Args:
    query: Free-text filter over name + description (case-insensitive
        substring). Omit to list everything, newest first.
    limit: Max results (1–100, default 20).
    offset: Pagination offset.

Returns:
    A list of open buy requests. Each includes ``id``, ``name`` (plus a
    deprecated ``title`` mirror of it),
    ``description`` (markdown — read the full text for specs and
    constraints), ``quantity``, ``max_price`` + ``currency`` (if the
    poster set a ceiling), ``contact`` (if they left an
    email/phone/handle), ``reference_url`` (sample or datasheet link
    if any), ``posted_by`` (display name), and ``created_at``.

    If the poster left a ``contact`` value, that's how a supplier
    should respond — Partle doesn't broker the conversation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses rate limiting (100 req/hour), no authentication, public visibility, and that Partle doesn't broker contact. It also explains response semantics like deprecated title and markdown descriptions, adding significant value.

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 somewhat long but well-structured with intro, usage guidance, Args, and Returns sections. Every sentence adds value, but it could be tightened slightly; the length is justified by the complexity.

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?

Covers all essential context: use case, public/private distinction, read-only and auth, rate limit, parameters, full return fields, markdown behavior, and how to respond. Highly complete for a read-only search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully documents each parameter: query as case-insensitive substring filter with omit behavior, limit with range and default, offset for pagination. This fully compensates for the schema gaps.

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 the tool browses public buy requests, the demand side of Partle, differentiating from product search (supply side). It names the exact resource and scope, explicitly distinguishing from sibling tools like search_products and create_buy_request.

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?

Provides clear context: use when offering matches by cross-referencing with search_products, or surveying unmet demand. It also notes buy requests are public sales-facing ads, unlike private inventory. However, it doesn't explicitly state exclusions (when not to use) beyond the implied demand/supply split, so not a full 5.

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

All Partle 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.