Skip to main content
Glama

itchio_browse_options

Read-only

Discover the visible filters and sorts of one native itch.io catalog context and return the classification, path, current facet values, all filter groups with their native destination paths and selected markers, the five native sort choices, the classification's tag-discovery endpoint and the open-tag-vocabulary flag. Set path to a relative catalog path such as /games or /books/top-rated, or a filter destination from an earlier response; follow the returned paths unchanged. Tags are an open creator vocabulary, so picker suggestions are discovery rather than a closed allowlist; actions distinguish selecting/replacing, appending and clearing a filter.

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": {
      "path": "<path>"
    },
    "name": "itchio_browse_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRequired relative native catalog path such as /games, /books/top-rated, or any filter destination returned by an earlier response. The response returns the visible filter groups, selected facets, native sort choices and the classification's tag-discovery endpoint.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that filter actions differ in kind (selecting/replacing vs appending vs clearing) and that tags come from an open creator vocabulary so picker suggestions are discovery, not a closed allowlist. That is genuine semantic context an agent cannot get from the annotations. It stops short of saying how selected markers or sort defaults behave, keeping it at a 4 rather than 5.

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?

The purpose and return payload are front-loaded in the opening clause, and the operational constraints follow in the second. It is dense but nearly every clause carries information; the enumeration of return fields is long, though it substitutes for an unread output schema.

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 one-parameter discovery tool with an output schema and read-only annotations, the description covers purpose, valid inputs, path-chaining discipline, and the semantics of the returned filter vocabulary. Nothing an agent needs in order to call it is missing, though the meaning of the selected markers and the open-vocabulary flag could be spelled out slightly more concretely.

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?

With a single parameter at 100% schema coverage the baseline is 3, but the description adds meaning: the path may be a catalog path or a filter destination echoed in an earlier response, and it must be followed unchanged. The 'do not rewrite the returned path' constraint is useful guidance the schema itself does not state.

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

Purpose5/5

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

The description names a specific verb (discover/return) and a precisely bounded resource: the visible filters and sorts of ONE native itch.io catalog context. It then enumerates exactly what comes back (classification, path, facet values, filter groups with destination paths and selected markers, five sort choices, tag-discovery endpoint, open-vocabulary flag), which is far more specific than a sibling name alone could convey.

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?

It gives concrete usage conditions: pass a relative catalog path like /games or /books/top-rated, or a filter destination harvested from a prior response, and follow returned paths unchanged. What is missing is an explicit statement of when NOT to use this tool versus the browse/catalog siblings, but the chaining guidance is clear enough to select it correctly.

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.