Partle Marketplac

get_my_inventory

Read-only

List the caller's personal inventory items.

Authenticated. Required OAuth scope: `inventory:read` (or pass an
`api_key` for legacy/programmatic clients).

Use this when the user asks "what do I own?", "what's on my
wishlist?", "what am I selling?", etc. The returned rows include
every status by default; pass `status` to filter.

Args:
    status: Filter by lifecycle. One of: ``owned``, ``wanted``,
        ``for_sale``, ``sold``, ``discarded``. Omit for all.
    product_id: Filter to rows linked to a specific Partle product.
    project: Exact-match filter on the project tag.
    q: Substring search on `name` and `notes` (case-insensitive).
    limit: Page size, 1–200. Default 50.
    offset: Pagination offset. Default 0.
    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. Omit when using OAuth.

Returns:
    ``{"items": [...], "count": int}`` where each item carries
    status, quantity, name (or linked product), notes, prices, etc.
    On auth failure: ``{"error": ...}``.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No
`limit`	No
`offset`	No
`status`	No
`api_key`	No
`project`	No
`product_id`	No

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral context: OAuth scope requirements, api_key fallback and override semantics, the nuance that an invalid/revoked token still fails, default status behavior, pagination limits, and the exact return shape including error handling. This goes well beyond what annotations provide.

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 organized with a clear opening line, an auth section, a usage cue, a labeled Args block, and a Returns block. Each sentence serves a distinct purpose—no fluff. The length is justified by the tool's complexity (7 params, auth fallback, output format).

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 7 parameters, no output schema, and auth complexity, the description covers everything needed: authentication/scope fallback, filtering semantics, pagination, return format, and error behavior. An agent can confidently invoke this tool without additional context.

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 has 0% description coverage, so the description must compensate, and it does thoroughly. Every parameter is explained with additional meaning: status enums are listed, q is defined as case-insensitive substring search on name/notes, limit has a 1–200 range, project is an exact-match filter, and api_key's override behavior is fully described. This exceeds what the raw schema would convey.

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 'List the caller's personal inventory items,' which is a specific verb and resource that clearly distinguishes this from sibling tools like get_my_products or search_products. It also immediately frames the scope as personal inventory, eliminating ambiguity.

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?

Explicitly states when to use the tool with user-phrase examples ('what do I own?', etc.) and explains the default behavior of returning all statuses. It lacks explicit exclusions or named alternatives (e.g., 'use get_my_products for product listings'), but the context is clear enough for an agent to select this tool appropriately.

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?