Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

itchio_jams_results_options

Read-only

Discover the complete visible ranking-criteria menu for one itch.io game jam and return the path, jam title, canonical jam URL and every criterion's label, consuming results path and selected/default flag, in source order. Pass the root relative /jam/slug/results path linked from jam browse's results_url; criterion child paths are not accepted here. Hosts define their own criteria (an automatic Overall, a primary voted criterion or manual rankings), so follow the returned paths with itchio_jams_results rather than guessing labels or slugs; unranked jams may have no results link, and hidden or unpublished results are unavailable.

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_jams_results_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRequired native relative destination from the previous jam response, e.g. /jam/gmtk-jam-2026/results for criteria discovery, /jam/gmtk-jam-2026/entries for submissions, /jam/godot-wild-jam-99 for the overview, or /jam/gmtk-jam-2026/rate/4794047 for submission metadata. Pass it unchanged; hidden/unpublished resources return 404 and unsupported destinations are rejected.

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.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavior — results are host-defined (automatic Overall, primary voted criterion, or manual rankings), output is in source order, and missing/unpublished results are unavailable. It also discloses that criterion child paths are rejected, which is a constraint not visible in the annotations.

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 and return shape are front-loaded, and every clause (path constraint, follow-up routing, unranked/hidden caveat) contributes. It is dense and slightly long for a one-parameter tool, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still summarizes them. Combined with the path constraint, host-defined criteria caveat, and follow-up tool routing, an agent has everything needed to call this correctly.

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 schema already carries most semantics. The description still adds value by specifying that the path must be the root /jam/slug/results destination obtained from results_url, and that criterion child paths are not accepted here.

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?

States a specific verb and resource: 'Discover the complete visible ranking-criteria menu for one itch.io game jam', then enumerates the returned fields. It is clearly differentiated from the sibling itchio_jams_results, which is named as the follow-up for actually reading rankings.

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

Usage Guidelines5/5

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

Explicitly says to pass the root relative /jam/slug/results path linked from jam browse's results_url, that criterion child paths are not accepted here, and to follow returned criterion paths with itchio_jams_results rather than guessing slugs. It also flags the when-not case: unranked jams may have no results link and hidden/unpublished results are unavailable.

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