Skip to main content
Glama

AskFur pet devices (pre-launch)

Get one AskFur product

get_product
Read-only

Full public details of one product: description, highlights, confirmed specs, planned app features and customisation. Concept products have no price or delivery date because none is confirmed.

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": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug from list_products, for example the last part of its page link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the safety hints provided by annotations, the description provides critical context regarding the data returned, notably that 'Concept products have no price or delivery date because none is confirmed.' This manages user expectations regarding data availability.

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?

The two sentences are highly effective, with the first sentence outlining the benefits of the data and the second addressing a specific, critical data constraint for concept products. It is concise and well-structured.

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?

Since there is no output schema, describing the various types of data returned (description, highlights, confirmed specs, planned features) is essential for agent completeness. It sufficiently covers the scope of the retrieval and its limitations.

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

Parameters4/5

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

Although the schema provides a detailed description, the text reinforces its purpose by noting the slug is 'Product slug from list_products' and gives an example of its format (last part of page link), adding contextual meaning to the parameter.

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?

The description clearly states the purpose is to retrieve full public details for a single product. While it doesn't explicitly differentiate from sibling tools like list_products in the text, the verb 'get' and the concept of 'one product' define its scope adequately.

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 focuses on what the tool returns rather than providing explicit rules for when to use it over alternatives. Its usage is generally implied by its singular function compared to list_products.

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