Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_items

Read-only

Searches the Dota 2 item table and returns compact summaries: key, id, display name, quality, gold cost, behavior, cooldown, mana cost, components, active and passive abilities and numeric attributes. Provide q (key or name search), quality (values are listed in the qualities field) and limit (default 50). Use it to look up what an item does or costs; use opendota_constants item_ids to decode item ids in match data.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional case-insensitive search on the item key or display name, for example blink.
limitNoOptional number of items to return, 1 to 500; defaults to 50.
qualityNoOptional item quality from the qualities list in the response, for example epic.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the useful scoping facts of a default limit of 50 and the set of fields returned. It doesn't discuss ordering, truncation behavior, or whether the limit caps total results, which is the one remaining gap for a paged-ish list tool.

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 purpose and return shape, then parameters, then a sibling cross-reference. No sentence is filler or duplicative of the others.

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

Completeness5/5

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

An output schema exists, so return values needn't be spelled out, yet the description still summarizes them helpfully. With three optional params, annotations covering safety, and an explicit sibling pointer, an agent has everything needed to call this correctly.

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 coverage is 100%, so all three parameters are already documented in-schema and the description largely restates them (q, quality, limit default 50). The one value-add is the pointer that quality values come from a "qualities" field, but the phrasing is ambiguous about whether that field belongs to this tool's response or a sibling's data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the Dota 2 item table") and enumerates the returned fields, so an agent knows exactly what it gets back. It also distinguishes itself from the constants/id-decoding sibling at the end of the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ("look up what an item does or costs") and names the alternative for a different need ("use opendota_constants item_ids to decode item ids in match data"). The routing decision is handed to the agent with no inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources