Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

itchio_jams_submission

Read-only

Read public metadata for one itch.io jam submission and return the native path, jam/project identity, project URL, title, optional summary, submitter credit links and text, results availability and the published per-criterion rank/score/raw-score table in source order. Pass the native relative /jam/slug/rate/project-id URL from jam submissions or published results; the numeric component is the project game.id, not the separate entry id. Manual scores retain literal n/a and ranks/scores stay strings; results_available false with an empty scores list means the anonymous page publishes no table, not that private or future results do not exist. Individual votes, judge feedback, comments, custom answers and account actions are excluded.

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

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.2/5.0
Behavior3/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 covered. The description still adds real behavioral detail beyond them – literal "n/a" for manual scores, ranks/scores kept as strings, and that results_available=false with an empty list means the anonymous page publishes no table rather than results not existing. It doesn't cover pagination or return-size behavior.

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 what the tool returns, then path-sourcing, then caveats. Dense but every sentence carries format or semantics information; the long return-value enumeration is the one part that could be trimmed given an output schema exists.

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?

Complete for a single-resource read tool: the path source, the field semantics (string ranks, literal n/a), the empty-results edge case, and the exclusions are all covered, and return shape is backed by an output schema.

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, but the description adds meaning the schema does not: the numeric URL component is the project game.id, not the separate entry id, and the path must be passed unchanged.

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 ("Read public metadata for one itch.io jam submission") and enumerates the returned fields, so an agent can tell it apart from sibling list/overview tools like itchio_jams_entries or itchio_jams_results without opening 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 Guidelines4/5

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

Gives clear context: take the native relative /jam/slug/rate/project-id path from jam submissions or published results, and explicitly excludes individual votes, judge feedback, comments, custom answers and account actions. It stops short of naming which sibling to call first, so the routing is implied rather than spelled out.

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