Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

speedrun_resource_options

Lists supported Speedrun metadata embeds, contextual ordering directions, and global timing method names by resource path to plan game-specific queries without account requests.

Instructions

Discover Speedrun contextual resource options. Lists supported metadata embeds, contextual ordering directions and global timing method names by resource path. Game detail supplies per-game timing support. No upstream collection or account request is made.

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": "speedrun_resource_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: 'No upstream collection or account request is made,' telling the agent this is a cheap, static lookup with no auth or network cost. It stops short of stating read-only semantics explicitly, caching behavior, or response shape, so coverage is partial rather than rich.

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 the core 'what it lists' content, with the no-request caveat placed last where it belongs. Dense and mostly waste-free, though the abstract phrasing 'contextual resource options' and 'by resource path' could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter discovery tool with no annotations and no output schema, the description should explain the shape of what comes back (a lookup keyed by resource path, presumably). It names the categories of data but leaves the return structure and the 'resource path' concept unexplained, 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?

The tool has zero parameters, which sets a baseline of 4; there are no argument meanings the description needs to explain. The stray reference to 'resource path' does not map to any input, adding minor confusion rather than clarity.

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 description gives a concrete inventory of what the tool returns: supported metadata embeds, contextual ordering directions, and global timing method names. That is more than a restatement of the name, though the phrase 'by resource path' is puzzling given the tool takes no parameters, and nothing in the text separates it from the many sibling speedrun_* tools.

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 only implied: the agent must infer that this is a discovery/preflight call to consult before composing other resource requests. The one routing hint ('Game detail supplies per-game timing support') points away to a sibling for a specific case, but there is no explicit when-to-use or when-not-to-use statement and no prerequisites are described.

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