Partle Marketplac

mark_sold

Idempotent

Mark an inventory item as sold (status=sold).

Convenience wrapper over `update_inventory_item` for the natural
"I sold the drill" request.

Authenticated. Required OAuth scope: `inventory:write`. Caller must
own the item.

Args:
    item_id: ID of the inventory row.
    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 updated inventory row, or ``{"error": ...}``.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No
`item_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations, the description discloses authentication requirements, required OAuth scope, ownership condition, the api_key override behavior, and the invalid-token failure mode. It also notes the return type, providing substantial safety-relevant 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 well-organized with clear sections for args and returns. Each sentence adds meaningful information—purpose, wrapper role, auth, parameter details, and output—without unnecessary fluff.

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?

For a two-parameter tool with no output schema, the description is fully self-contained: it explains purpose, usage context, authentication, ownership, parameter semantics, and return value. There are no obvious gaps given the tool's simplicity.

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?

Despite zero schema description coverage, the description fully explains both parameters: 'item_id' as the inventory row ID, and 'api_key' with its purpose, override behavior, and failure conditions. This compensates completely for the schema's lack of descriptions.

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 opens with a specific verb and resource: 'Mark an inventory item as sold (status=sold).' It differentiates from siblings like 'mark_for_sale' and 'update_inventory_item' by framing itself as a convenience wrapper for the natural 'I sold the drill' 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?

The description clearly indicates when to use the tool: for natural-language 'sold' requests, and references 'update_inventory_item' as the underlying alternative. However, it does not explicitly state when NOT to use it or list other alternatives, so it falls short of a perfect score.

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

All Partle Marketplac 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?