Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_options

Discover itch.io game-jam filters, sorts, selected choices, and clear-filter paths, plus native browse links at /jams so you can follow returned URLs without guessing parameters.

Instructions

Discover itch.io game-jam filters and sorts. Returns every visible filter-group value, selected choice, clear-filter path and contextual sort. At /jams returns native landing-page browse links. Follow returned paths without guessing parameter translations. Account, hosting, joining and rating operations are excluded.

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

Input Schema

NameRequiredDescriptionDefault
pathNoNative relative jam destination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior3/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. It does disclose the return contents (filter values, selected choice, clear-filter path, sort) and a page-specific behavior at /jams, but says nothing about auth requirements, rate limits, or whether selection state is read-only — gaps that matter for a tool with zero annotation coverage.

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?

Four short sentences, front-loaded with what is discovered and immediately followed by what is returned and two operational constraints. Dense but every sentence carries information; the middle list of return fields is the only slightly clunky part.

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 single optional-parameter discovery tool with no output schema, the description covers purpose, returned artifacts, and one special-case route. It leaves the precise shape of the returned filter groups and paths undocumented, which is the main remaining gap.

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?

With one optional parameter at 100% schema coverage the baseline is 3, but the description adds real meaning: the path is a "native relative jam destination" that is typically a link this tool itself returned, and the agent is told to follow it rather than reconstruct query parameters. That is provenance the schema alone does not supply.

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?

"Discover itch.io game-jam filters and sorts" gives a specific verb and resource, and the second sentence details exactly what the tool surfaces (filter-group values, selected choice, clear-filter path, contextual sort). It does not name a sibling such as itchio_jams_browse or itchio_jams_results_options to draw a hard boundary, so it falls short of a 5.

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?

The description scopes the tool by exclusion ("Account, hosting, joining and rating operations are excluded") and instructs the agent to "follow returned paths without guessing parameter translations," which tells the agent how to act on the result. It stops short of explicitly naming which sibling to use for jam browsing/results instead.

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