Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_overview

Retrieve an itch.io game jam's overview, including identity, dates, voting deadline, hosting links, description, status, banner, statistics, and navigation metadata without account actions.

Instructions

Read itch.io game-jam overview. Returns the jam's native identity, date strings, optional voting deadline, hosting credits/links, description text, status text, banner, display statistics and navigation. Preserves upcoming, active, voting and finished page metadata without computing a phase or countdown. Account and participation 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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesNative relative /jam/slug destination from jam browse

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it declares the tool is a pure read, that it preserves page metadata across upcoming/active/voting/finished states 'without computing a phase or countdown', and that account/participation actions are excluded — useful behavioral boundaries an agent would otherwise have to guess. It stops short of covering auth requirements or error behavior for an invalid path, which keeps it from a 5.

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

Conciseness5/5

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

Three sentences, front-loaded with the action, followed by a compact return-field inventory and a scope exclusion. The long field list is dense but every item conveys what the caller gets back; there is no filler or restatement of the title.

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?

With no output schema and no annotations, the description must describe return contents and safety posture, and it does both — naming the returned data categories and clarifying that no phase or countdown is computed. The only gap is that it does not address failure modes or how the caller should interpret the returned navigation field.

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?

There is one parameter with 100% schema description coverage; the schema explains it is a 'Native relative /jam/slug destination from jam browse', which is the key detail. The description adds no further meaning about the path argument, so the baseline 3 applies.

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 first sentence gives a specific verb and resource ('Read itch.io game-jam overview'), and the enumeration of returned fields (identity, dates, voting deadline, credits, description, status, banner, stats) makes the tool's scope concrete. The closing exclusion of 'account and participation actions' implicitly separates it from itchio_jams_submission and entries tools without naming them, so sibling differentiation is present but indirect.

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?

Usage context is only implied: the schema says the path comes 'from jam browse', suggesting this fetches detail for a single jam found via itchio_jams_browse. The description never states when to use this versus browse, entries, results, or options, and offers no prerequisites. It states a scope exclusion but not a selection rule.

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