Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_browse

Browse itch.io game jams by timing, voting, featured, or participation filters and native sorts, returning structured cards with host links, dates, counts, and page links.

Instructions

Browse itch.io game jams. Follows native timing/voting/featured/participation filters and context-specific sorts. Preserves source cards, host links, dates, display counts, result links, ordering and page links. Explicit empty pages return an empty array. The /jams landing grid supports page1 only and has no pagination field.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based native page
pathNoNative relative path from jam options

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, the description carries the full burden and does disclose real behavior: explicit empty pages return an empty array, the landing grid is unpaginated, and source cards/host links/dates/counts/ordering/page links are preserved. What is missing is any statement of auth, rate limits, or whether the crawl is read-only, but the key output-shape contract is present.

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?

Four short sentences, front-loaded with purpose, then filters/sorts, then the return contract, then the pagination caveat. No filler or restated 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?

There is no output schema, so the description must describe what comes back, and it does so compactly (source cards, host links, dates, display counts, result links, ordering, page links) plus the empty-result and page-1-only edge cases. The remaining gap is the relationship between the two optional parameters, which is left to the schema.

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 description coverage is 100%, so the schema already defines page as a one-based native page and path as a native relative path. The description adds a little meaning by tying path to 'jam options' and noting the landing grid accepts page 1 only, but it does not explain how path and page interact or give path examples.

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?

"Browse itch.io game jams" gives a specific verb and resource, and the following sentences narrow it to a filter/sort-preserving listing tool. It never names a sibling (e.g. itchio_jams_entries or itchio_jams_results) to contrast with, so an agent must infer the boundary from names alone.

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?

It implies usage through the mention of native timing/voting/featured/participation filters and context-specific sorts, and flags that the /jams landing grid is page-1 only. There is no explicit when-to-use statement or named alternative for entry lists versus result pages, so the guidance is implied rather than stated.

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