Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

hearthstone_card

Read-only

Get one public Hearthstone card from Blizzard's card library by its numeric card ID and return the source card fields together with the library response's page metadata. Use hearthstone_cards for filtered listing and hearthstone_card_filters to discover the dynamic gallery selectors.

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": {
      "id": "<id>"
    },
    "name": "hearthstone_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired numeric card ID from the public Hearthstone card library, for example 80818. This is the library card id, not a deck or gallery slug.

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/external-call profile is covered by structured data. The description adds that the card comes from Blizzard's public library and that results include source card fields plus the library response's page metadata, but says nothing about failure behavior for an invalid or missing ID. With annotations doing the heavy lifting, this modest addition is a 3.

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 compact sentences with zero filler: identity/scope first, then sibling routing. Every clause earns its place and the most decision-relevant information is front-loaded.

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-parameter read tool with an output schema and annotations present, the definition covers purpose, routing, and the parameter sufficiently. The only small gap is no guidance on what happens with a nonexistent or malformed card ID, which matters for a lookup-by-key tool.

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 id parameter is already fully documented as a numeric library card id (not a deck or gallery slug). The description restates 'numeric card ID' without adding new constraints or format detail beyond the schema. Baseline 3 applies when the schema does the work.

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 — 'Get one public Hearthstone card from Blizzard's card library by its numeric card ID' — including scope (single card, public library). It immediately distinguishes itself from hearthstone_cards (filtered listing) and hearthstone_card_filters (selector discovery).

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 routes the agent: use hearthstone_cards for filtered listing and hearthstone_card_filters to discover dynamic gallery selectors. This is a clear when-to-use-this-vs-alternatives statement 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