Skip to main content
Glama
Sign In
Partle

Partle

by rubenayla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_product

Read-only

Retrieve complete product details including description, images, expiration, and sold status using the product ID from search results.

Instructions

Get the full record for a single product by its numeric ID.

Use this after search_products returns a candidate the user is interested in, when you need fields that aren't in the search summary (full description, all images, expiration, sold status). Don't loop get_product over many search results — re-search with tighter filters instead.

Read-only. No authentication.

Args: product_id: The integer id from a product returned by search_products or shown on a Partle product page URL.

Returns: A single product object with all fields, including the canonical partle_url to share with the user.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Adds behavioral context beyond annotations: 'Read-only. No authentication.' Also mentions return includes full fields and canonical URL, fully disclosing what the tool does.

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?

Well-structured: purpose, usage context, property note, returns. Every sentence is informative and necessary, with no redundancy.

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?

With one parameter, no output schema, and annotations providing readOnlyHint, the description covers purpose, when to use, parameter semantics, and return value completely. No gaps remain.

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?

Parameter product_id is described in detail: 'The integer id from a product returned by search_products or shown on a Partle product page URL.' This adds critical meaning beyond the schema, which only states type integer.

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 starts with 'Get the full record for a single product by its numeric ID,' providing a clear verb+resource. It distinguishes from siblings like search_products (which returns summaries) and get_my_products (own products).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: after search_products when more fields are needed. Also warns against looping over many results and suggests re-searching instead, providing clear when-not-to-use guidance.

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