Skip to main content
Glama

AskFur pet devices (pre-launch)

List AskFur products

list_products
Read-only

AskFur's pre-launch catalogue of connected pet devices and essentials for cats and dogs: name, tagline, category, stage (concept or launched) and page link. Concept products are previews, not for sale.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly this category: device (connected devices) or essential (everyday gear). Leave out for all products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context beyond that: the catalogue is pre-launch, entries carry a stage of concept or launched, and concept products are previews that cannot be purchased — a caveat that prevents misrepresenting inventory as buyable.

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 short sentences, front-loaded with what the catalogue is and what fields come back, then the one caveat that matters. No filler, no repetition of the parameter description.

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 zero-required-parameter, read-only list tool with no output schema, the description usefully enumerates the return fields and flags that concept entries are non-sellable. Minor gaps remain around ordering, result volume, and how this differs from fetching a single product.

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 single enum parameter is fully described in the schema, including the leave-out-for-all behavior, so the baseline is 3. The description repeats the two categories but adds no filtering syntax, combination rules, or edge-case meaning beyond what the schema already states.

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 resource and scope: AskFur's pre-launch catalogue of connected pet devices and essentials for cats and dogs, and enumerates the returned fields (name, tagline, category, stage, page link). It is unambiguous what the tool returns, but it does not name or distinguish itself from the sibling get_product, which also concerns products.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternatives get_product or join_waitlist. The only usage-shaped statement, 'Concept products are previews, not for sale,' is a data caveat rather than routing advice, so an agent must infer that this is the browse-all endpoint.

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