Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jam_calendar

Retrieve the itch.io game-jam calendar with source IDs, detail URLs, dates, participant counts, and featured flags to plan jams or track public listings.

Instructions

Get itch.io game-jam calendar. Returns every jam in the public calendar payload, preserving source IDs, relative detail URLs, dates, joined counts, hue and optional featured/highlight values. Dates remain source strings. The calendar is a source-selected window, not an exhaustive archive. Participant, duration and featured UI filters operate locally and are not server query parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "itchio_jam_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 substantial work: it discloses the returned fields, warns that dates stay as source strings (no normalization), and frames the payload as a window rather than an exhaustive archive. It does not cover pagination, caching, or rate-limit behavior, which keeps it short of 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.

Conciseness4/5

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

Purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct caveat (field preservation, date format, scope, local filters). The field enumeration in sentence two is somewhat listy but every clause is informative.

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 zero-parameter read tool with no output schema and no annotations, the description supplies the return shape and scope limits an agent needs to call and interpret it. Only operational details such as caching or result-size limits are absent, which are minor here.

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?

The tool takes zero parameters, so the baseline is 4. The description goes slightly beyond by preemptively clarifying that participant, duration and featured filters are client-side and cannot be passed as query parameters, which heads off a likely agent error.

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?

Opens with a specific verb and resource ("Get itch.io game-jam calendar") and scopes the result set to the public calendar payload. It does not name any sibling (e.g. itchio_jams_browse, itchio_jams_results) to draw an explicit contrast, so the distinction is inferable but not stated.

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 is implied by the resource name and the note that the calendar is a source-selected window, but there is no explicit when-to-use/when-not guidance or pointer to an alternative tool for exhaustive jam listing. The statement that filters are local rather than query parameters is the closest thing to a usage constraint.

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