Partle

create_buy_request

Post a public buy request — an ad asking suppliers to reach out.

Use when the user wants others to know they're looking to buy
something. **Independent of personal inventory** — inventory is the
user's private workshop tracking; a buy request is a sales-facing
ad on the public demand feed at /wanted.

Authenticated. Required OAuth scope: ``inventory:write``.
**Not idempotent** — each call creates a new public post.

Args:
    name: Short scannable headline ("Looking for X"). Required.
    description: Plain text long-form — specs, constraints, delivery
        preference. The supplier reads this to decide whether they
        can fulfil.
    quantity: How many units the poster wants. Default 1.
    max_price: Optional ceiling per unit.
    currency: Currency for max_price (default €).
    contact: Free-form contact (email/phone/Telegram/etc.) shown
        publicly. Optional. Without it, suppliers can only respond
        via whatever channels you separately make available.
    reference_url: Link to a sample/datasheet/manufacturer page.
    product_id: Link to a canonical Partle product if asking for a
        specific known SKU.
    api_key: Optional API key (`pk_*`, generate at /account).
        Used when there is no OAuth token, and also when the OAuth
        token lacks the required scope — an explicitly passed key
        overrides an ambient token that is scoped too narrowly.
        An invalid or revoked token still fails regardless.

Returns:
    The newly-created buy request, or ``{"error": ...}``.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	No
`api_key`	No
`contact`	No
`currency`	No	€
`quantity`	No
`max_price`	No
`product_id`	No
`description`	No
`reference_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 30, 2026

removedInput schema / properties / title

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Title"
-}

Changed5 schema fields changedAug 8, 2026

addedInput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Name"
+}

addedInput schema / properties / title / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / title / default
```
Added value: +null
```
removedInput schema / properties / title / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "title"
-]
```

AddedMay 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the call is not idempotent, requires authentication with a specific OAuth scope, and explains how api_key overrides narrow tokens. It also states that invalid tokens still fail and that each call creates a new public post—useful behavioral context.

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?

The description is front-loaded with the core purpose and usage trigger, followed by authentication constraints, detailed argument semantics, and return behavior. Each sentence adds value; the structured Args block makes the long definition scannable.

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?

Given no output schema, the description still states the return value shape ('newly-created buy request, or {error: ...}'), covers authentication and override behavior, and explains the public feed context. An agent has enough information to select and invoke the tool correctly without additional lookup.

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%, yet the description documents all 9 parameters with meaningful guidance: name is called required, quantity defaults to 1, max_price is a per-unit ceiling, and contact explains the public visibility and supplier-response implications. This fully compensates for the bare schema.

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 states a specific verb and resource: 'Post a public buy request — an ad asking suppliers to reach out.' It clearly distinguishes the tool from inventory management and identifies the public demand feed at /wanted, so an agent can tell it apart from siblings like add_inventory_item and search_wanted.

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?

'Use when the user wants others to know they're looking to buy something' gives a clear trigger condition. It also explicitly separates buy requests from personal inventory, preventing cross-tool confusion, though it does not name a specific alternative tool to use instead.

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.

create_buy_request

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources