Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_browse_options

Discover visible itch.io catalog filters and native sort choices for a path, along with current facet values and tag references, to preserve browsing context.

Instructions

Discover itch.io catalog filters and sorts. Returns all visible filter groups, source destination paths, five native sort choices, the current facet values and a tag-discovery reference. Tags form an open vocabulary; suggested tags are not an exhaustive list of creator tags. Follow returned paths to preserve the selected context.

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
pathYesRelative native catalog path, such as /games or /tools/newest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it enumerates the returned payload (filter groups, destination paths, five native sort choices, current facet values, tag reference) in lieu of an absent output schema. It also flags a real behavioral caveat that suggested tags are not exhaustive because tags are an open vocabulary, plus a context-preservation constraint on the returned paths. It stops short of stating failure behavior for an invalid path or any read-only confirmation, but the core disclosure is well above baseline.

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?

Purpose is front-loaded in the opening sentence, followed by return contents, then a caveat, then an instruction — a sensible order with no filler. The return-content list is long, but each item names a distinct part of the payload rather than padding.

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, read-only discovery tool with no annotations and no output schema, the description compensates well by describing what comes back and warning about the open tag vocabulary. Only minor gaps remain, such as what happens with an unrecognized path and explicit confirmation that no catalog state is mutated.

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 `path` parameter is fully documented with an example, so the schema does the heavy lifting. The description adds modest meaning by implying that valid `path` values come from the 'source destination paths' this tool returns and should be followed to preserve context, but it gives no format or validation detail 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?

The first sentence gives a specific verb and resource: 'Discover itch.io catalog filters and sorts,' which pins down that this is a metadata/discovery tool returning filter and sort options rather than result listings. It does not name a sibling, but its output inventory (filter groups, sort choices, facet values) implicitly separates it from browse-style siblings such as itchio_browse without the agent needing to open a schema.

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?

Usage is only implied: the agent can infer it should call this before browsing to learn available filters and sorts, and the closing sentence gives workflow guidance ('Follow returned paths to preserve the selected context'). There is no explicit statement of when not to use it or which sibling to call instead once facets are chosen.

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