Skip to main content
Glama

One of my products

get_my_product
Read-onlyIdempotent

One product from list_my_products in full: its description, tags, prices, the text printed on its insert card, where it is published, and each variant with its price and photos. Use it before suggesting better photos or a better description. Needs a connected Printlooper account.

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_my_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesproduct_id from list_my_products

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description does not contradict them. Beyond that it discloses an auth prerequisite ('Needs a connected Printlooper account') and, since no output schema exists, explains what the response actually contains rather than just saying it's a read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence leads with the core action and then enumerates the payload, followed by one short usage sentence and one prerequisite sentence. No filler, though the long comma-separated field list is slightly run-on.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating returned fields, and it names the account prerequisite for a simple one-parameter read. Nothing essential to invoking it correctly appears missing, though error or empty-result behavior is unaddressed.

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

Parameters3/5

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

There is one parameter with 100% schema description coverage, and the schema already states 'product_id from list_my_products'. The description's 'One product from list_my_products' only echoes that provenance and adds no format or constraint detail, so the baseline 3 applies.

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?

States a specific verb and resource ('one product from list_my_products in full') and enumerates exactly what 'in full' means: description, tags, prices, insert card text, published locations, and variants with price and photos. This clearly distinguishes it from the sibling list_my_products, which returns the list rather than the full record.

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?

Gives an explicit usage context: 'Use it before suggesting better photos or a better description,' which ties it to the photo/description improvement workflow involving siblings like add_product_photos. It does not state when not to use it or name an alternative for other purposes, but the situational guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources