Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stan Store product

stan_store_product_get
Read-onlyIdempotent

Fetch a single Stan Store product by handle and slug, returning price, stock, questions, reviews, and booking settings for product research and verification.

Instructions

Get one Stan Store product with its price, stock, questions, reviews and booking settings. Requires handle and slug.

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": {
      "handle": "<handle>",
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stan_store_product_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Product slug from a product page, e.g. `retirement-bingo`. Case-insensitive at Stan; the canonical slug is returned.
handleYesRequired. Stan Store handle, with its canonical case. Letters, numbers, dots, underscores and hyphens; 2 to 47 characters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value by disclosing which data facets come back, but says nothing about failure modes for invalid handle/slug or the open-world network dependency.

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?

Two sentences, front-loaded with the resource and return contents, followed by the required inputs. No filler or redundancy.

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?

For a five-parameter read tool with no output schema, the description covers what is fetched and what is required. The analytics/conversation parameters are well documented in-schema, so the only gap is that nothing tells the agent when to prefer this over the availability or list siblings.

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 description coverage is 100%, so both domain parameters are fully documented in-schema, including the canonical-case note for handle. The description only restates that handle and slug are required and adds no semantics of its own; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one Stan Store product') and enumerates the returned facets (price, stock, questions, reviews, booking settings). 'One' implicitly contrasts with the list sibling, but no sibling is named explicitly, so differentiation is left to inference.

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

Usage Guidelines3/5

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

The singular 'one product' hints this is the single-record path rather than stan_store_products_list, and 'Requires handle and slug' signals prerequisites. However, there is no explicit when-to-use/when-not guidance and no pointer to stan_store_product_availability_get for stock-only lookups.

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