Skip to main content
Glama
Sign In
Partle

Partle

by rubenayla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mark_sold

Idempotent

Mark an inventory item as sold to update its status. Requires the caller to own the item.

Instructions

Mark an inventory item as sold (status=sold). Caller must own it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>",
      "item_id": "<item_id>"
    },
    "name": "mark_sold"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, idempotent operation. The description adds the ownership precondition, which is useful. However, it does not discuss side effects, error conditions, or idempotency implications 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 a single, well-structured sentence that front-loads the action and key condition. Every word adds value, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple mutation tool with only two required parameters and no output schema, the description covers the essential purpose and a precondition. However, it omits details like behavior if the item is already sold or not found, which could lead to incorrect usage.

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

Parameters2/5

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

Schema coverage is 0%, meaning the description adds no explanation for the two parameters ('api_key' and 'item_id'). The description does not clarify their purpose or any constraints, so the agent must rely entirely on the schema, which is insufficient for effective use.

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 verb 'Mark' and resource 'inventory item', specifies the status change to 'sold', and includes a precondition 'Caller must own it'. This distinguishes it from sibling tools like 'mark_for_sale' or 'delete_inventory_item', providing specific purpose clarity.

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 includes a precondition ('Caller must own it'), which helps the agent determine when to use the tool. However, it does not explicitly state when not to use it or mention alternative tools for other status changes, leaving some ambiguity.

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

Deploy Server

Other Tools