Skip to main content
Glama

Try product for free

try_product

Run a product on its built-in example input, free of charge. The answer also shows how to use it on your own input (the per-call price and x402 URL) and how to own it (the package and its kit bundle, when for sale).

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": {
      "slug": "<slug>"
    },
    "name": "try_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses that the run is free of charge, that it executes on a built-in example input rather than caller data, and that the response includes per-call price, an x402 URL, package/kit bundle and sale availability. It does not say whether the call has side effects, what happens on an unknown slug, or how the run result itself is shaped.

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 sentences, front-loaded with the action and the 'free' qualifier, then the response contents. The parentheticals are dense but each carries real information; nothing is padding.

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

Completeness3/5

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

For a one-parameter tool with no annotations and no output schema, the description covers the return contents unusually well, so the agent knows what to expect. The remaining hole is the sole input: nothing explains the slug, and no guidance is given for invalid or unknown slugs.

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

Parameters2/5

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

There is a single required parameter, slug, at 0% schema description coverage, and the description never mentions it. An agent must infer that 'the product' is identified by the slug; nothing tells it the expected form (product id vs name vs path) or how it is resolved. This is where the description most needed to compensate for the empty schema and did not.

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: run a product on its built-in example input, free of charge. That is clearly distinct from buy_product/order_product (purchase) and describe_product (information only), so an agent can route on it. The second sentence then explains what the response contains, which further sharpens the purpose rather than restating the title.

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?

Implies clear usage context: use this for a free trial run of a product, and it also surfaces pricing/ownership information for when you want to move to your own input or own it. It never names an alternative tool or states an exclusion (for example 'use buy_product to actually purchase'), so the routing is implied rather than explicit.

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