Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_results_options

Discover itch.io game-jam ranking criteria and return every visible criterion label with its native results path, including the default selection.

Instructions

Discover itch.io game-jam ranking criteria. Returns every visible criterion label and native results path for one jam, including the default/primary selection. Criteria are host-defined and may include manual rankings or Overall. Use a root /jam/slug/results path linked from jam browse. 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
pathYesRoot relative /jam/slug/results destination

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?

No annotations are supplied, so the description carries the full burden and mostly delivers: it discloses that criteria are host-defined, may include manual rankings or 'Overall', that the default/primary selection is flagged, and that hidden or unpublished results cannot be reached. The gaps are limited to output shape details and whether the call is strictly read-only.

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?

Four short sentences, front-loaded with the purpose, then the payload, then the path constraint, then the availability caveat. No filler; the only slight redundancy is restating the path format already present in the 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?

A simple one-parameter discovery tool with no output schema and no annotations; the definition covers what is returned, how to obtain a valid path, and the main failure condition. Only minor items (whether the response includes extra metadata, ordering of criteria) are left unstated.

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 parameter already carries a description nearly identical to the definition's wording, so there is little added meaning. The description does reinforce the constraint that the path must be a root /jam/slug/results destination obtained from jam browse, which is modest but real value.

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?

Names a specific verb and resource: 'Discover itch.io game-jam ranking criteria' and states the return payload ('every visible criterion label and native results path for one jam, including the default/primary selection'). This clearly separates it from a results-fetching tool, though it never names the sibling it complements (itchio_jams_results), leaving the split to inference from wording.

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?

Gives a usable precondition ('Use a root /jam/slug/results path linked from jam browse') and a negative constraint ('Hidden or unpublished results are unavailable'), which implies when the tool will be empty. However it never states explicitly when to call this versus the results tool, so the agent must infer the two-step workflow.

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