Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

itchio_jams_options

Read-only

Discover every visible game-jam filter and sort in one native itch.io browse context and return the path, filter-group labels with all native destination paths and active choices, each group's clear-filter path, the contextual sort options and the native links at /jams. path defaults to /jams/upcoming; at /jams the response contains the landing page's browse links rather than manufactured groups or sorts. Sort options depend on the selected timing context, and selecting a different filter can change canonical path order, so use the returned paths directly. Hosting, joining, rating, account and community operations are excluded.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional native relative jam destination returned by an earlier response, default /jams/upcoming. At /jams the response contains the landing page's browse links instead of manufactured filter groups.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. Beyond that, the description discloses meaningful behavior: the response shape is derived from a native itch.io browse context, /jams returns landing-page browse links rather than synthesized groups, and sorts are context-dependent with canonical paths that can reorder. It does not discuss failure modes for an invalid path, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and information-dense, but it is delivered as one sprawling sentence chain and the /jams caveat is stated twice (once in the description, once again in the schema's own description). Splitting the return shape from the usage caveats would make it more scannable without losing content.

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 single-parameter, read-only options-enumeration tool with full schema coverage, an output schema, and annotations, the definition provides enough: default behavior, the special-context behavior, ordering caveats, and an explicit scope boundary. The one thing an agent might still want — behavior on an invalid or stale path — is absent.

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?

Schema description coverage is 100% for the single parameter, so a baseline of 3 applies. The description goes further by stating the default, explaining the distinct semantics when path is /jams, and instructing the agent to feed returned paths back verbatim rather than constructing them — guidance that is not fully captured by the schema field alone.

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 uses a specific verb and resource ('Discover every visible game-jam filter and sort') and enumerates exactly what is returned (filter-group labels, native destination paths, active choices, clear-filter paths, sort options, /jams links). It does not, however, explicitly differentiate itself from the close sibling itchio_jams_results_options, which appears to cover the results-side options; the agent must infer the split from context rather than from the text.

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 a concrete starting context (path defaults to /jams/upcoming), explains the special case at /jams, and warns that sort options shift with the timing context and that canonical path order can change, so returned paths should be reused. It also lists exclusions (hosting, joining, rating, account, community). It stops short of naming which sibling to call instead for those excluded cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources