Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_team

Read-only

Returns one OpenDota team profile with its name, tag, logo, rating and rating delta, wins, losses and most recent match. Provide a positive team_id from opendota_teams or a match result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "opendota_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesRequired positive OpenDota team ID from opendota_teams or a match response.

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

A3.8/5.0
Behavior3/5

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

readOnlyHint/openWorldHint already declare the safety profile, and an output schema exists, so restating the returned fields (name, tag, logo, rating, rating delta, wins, losses, latest match) overlaps structured data. The description still adds the useful 'returns one entity, no pagination/list semantics' signal, but nothing about error behavior for an invalid ID.

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?

Two sentences, zero filler, with the returned content stated before the invocation prerequisite. Nothing to trim.

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 one-parameter read-only lookup whose return shape is covered by the output schema and whose safety profile is covered by annotations, the description covers what an agent needs. It omits only edge-case behavior (invalid or unknown team_id).

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% and the single parameter is fully documented in the schema, including the 'positive' constraint and provenance. The description repeats essentially the same provenance note rather than adding new detail, so baseline 3 applies.

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?

Uses a specific verb ("Returns") on a specific resource ("one OpenDota team profile") and enumerates the payload fields, so the agent knows exactly what it gets. It does not differentiate itself from nearby siblings such as opendota_team_matches, opendota_team_players or opendota_team_heroes, but the single-entity identity is unambiguous.

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 second sentence tells the agent where a valid team_id comes from (opendota_teams or a match result), which is the key prerequisite for invocation. It gives no explicit exclusions or when-to-use routing against the team_* siblings, so it stops short of full routing guidance.

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