Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_results

Read published itch.io game-jam ranking pages by criterion to capture native ties, scores, creator credits, submission links, and pagination for analysis.

Instructions

Read itch.io game-jam results. Reads a published per-criterion ranking page. Criteria must belong to the selected jam's live discovery menu. Preserves native ties, rank text, adjusted/raw score strings (including n/a), creator credits, submission links and relative pagination. No derived rankings or account actions.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based native page
pathYesRelative result destination from jam results options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/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 it does disclose meaningful return-fidelity behavior: native ties preserved, rank text and raw/adjusted score strings (including n/a) left untouched, creator credits and submission links returned, relative pagination. That tells an agent the tool does no normalization or derivation. Auth, rate limits, and error behavior are still undisclosed.

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?

Front-loaded with the purpose, then scope, then return guarantees, then exclusions — a logical order with no filler. The telegraphic sentence fragments are dense but readable; a slightly tighter grouping of the 'preserves…' list would be ideal.

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 two-parameter read tool with no annotations and no output schema, the description covers purpose, prerequisite validation, return-field fidelity, and scope exclusions — enough to call it correctly. The remaining gap is operational context (auth or failure modes), which is less critical for a read-only page fetch.

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 coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by constraining what 'path' may point to: the criterion must belong to the selected jam's live discovery menu. The pagination sentence also frames 'page' as a native, one-based 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?

States a specific verb and resource ('Read itch.io game-jam results') and narrows it to 'a published per-criterion ranking page', which separates it from an entries or overview tool. It does not explicitly name a sibling, but the negative scope ('No derived rankings or account actions') further fixes what it is not.

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?

Gives a genuine precondition — the criterion must exist in the jam's live discovery menu — which tells an agent it likely needs the results-options tool first. It also states two exclusions (no derived rankings, no account actions), though it never names the alternative tool to use for those cases.

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