Skip to main content
Glama
Sign In

Shootika

by com.shootika
OverviewDiscussionsAdmin

Get product

get_product
Read-only

Returns one product with its id, title, family, garment_category, accessory_kind, shoot_routes (on_model: shoot it on a model scene; placement: on a placement scene, the product alone; empty: it cannot be shot yet) and photos (each photo has an id, url and size). Use it to pick which photo to shoot and which kind of scene to list, or to check a product before a shoot. Fails with "not found" for an id that is not in this store.

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_idYesThe product id (a UUID) from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, so the bar is lower, and the description adds real value beyond them: it discloses the 'not found' failure for ids outside this store and explains that an empty shoot_routes means the product cannot be shot yet. It does not cover photo ordering or pagination, but for a single-record read that is minor.

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?

Front-loads the return shape, then use cases, then failure mode — a sensible order with no filler sentences. The long parenthetical listing shoot_routes semantics is dense but earns its place by preventing a wrong call.

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 no output schema, the description fully carries the return contract: it names every top-level field, the photos sub-fields, the meaning of each shoot_routes value, and the error case. An agent can call this correctly and interpret the response without further lookup.

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?

Schema coverage is 100% and the schema already states the id is a UUID from list_products, which the description does not extend with format or validation detail. Baseline 3 applies since the schema carries the parameter meaning.

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 ('Returns one product') and enumerates the exact fields returned, including the non-obvious shoot_routes values with inline semantics. It is unmistakably distinct from list_products and the write-side siblings like add_product.

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 concrete use cases: pick which photo to shoot, which scene kind to list, or pre-check a product before a shoot. It does not explicitly name list_products as the alternative for multi-product browsing, so the routing guidance is clear but not exhaustive.

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

All Shootika toolsInspect
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