Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stan Store product availability

stan_store_product_availability_get
Read-onlyIdempotent

Fetch available meeting slots or upcoming webinar sessions with open seats for a Stan Store product by providing its handle and slug.

Instructions

Get free meeting slots or upcoming webinar sessions with seats for one Stan Store product. 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_availability_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.
endDateNoLast day of the window as `YYYY-MM-DD`. Default: 14 days after `startDate`; the product's booking window caps it.
timezoneNoIANA timezone for the requested slots. Default: the product's own timezone.
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.
startDateNoFirst day of the window as `YYYY-MM-DD`. Default: today in the requested timezone.
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.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds the useful behavioral framing that results are bookable slots/sessions 'with seats,' but says nothing about empty result behavior, window capping, or the fact that the product's booking window can truncate the requested range — details left entirely to the schema.

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?

Two short sentences, front-loaded with the outcome the agent cares about, with no padding. The trailing prerequisite sentence is largely redundant with the schema and is slightly incomplete about the full required set, which costs a point.

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 an 8-parameter tool with no output schema, the description does convey what comes back (meeting slots / webinar sessions with seats) and names the two identifying inputs, while the schema carries the date-window, timezone and conversation_id mechanics. Reasonably complete, though it could note that availability may be empty or window-capped.

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 the baseline is 3. The only parameter content in the description ('Requires `handle` and `slug`') repeats what the schema already marks required, and notably omits that `context` and `llm_model` are also required, adding no new meaning.

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 concrete verb and resource: retrieves free meeting slots or upcoming webinar sessions with remaining seats for a single Stan Store product. That distinguishes it from the identity-oriented siblings like stan_store_product_get. It stops short of naming an alternative for the 'list bookable slots' use case, so it is clear but not sibling-differentiating at a 5 level.

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 description gives the precondition ('Requires `handle` and `slug`') but never says when to choose this over alternatives such as stan_store_product_get or a product-details tool, nor when not to call it. Usage is therefore only implied by the resource type rather than stated.

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