Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hearthstone_card

Fetch a Hearthstone card by numeric ID from the public card library to get the card record and pagination metadata in the upstream response shape.

Instructions

Get a Hearthstone card by ID. Returns one card from the public Hearthstone card library. The card record and pagination metadata preserve the upstream response shape.

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
idYesNumeric card ID from the Hearthstone card library

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 must carry the behavioral load, and it does disclose that the source is a public library and that the record and pagination metadata mirror the upstream response shape — useful passthrough context. It does not cover failure behavior for bad IDs, whether lookups are read-only and unauthenticated, or any rate limits.

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?

Three short sentences, front-loaded with the action and resource, with no redundant restatement of the name. The final sentence about preserving the upstream response shape is slightly vague but still earns its place by signalling passthrough semantics.

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 lookup with no output schema, the description covers what is fetched, from where, and the general shape of the return value including pagination metadata. Only error/edge-case behavior is left unaddressed, which is a minor gap at this complexity level.

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 the single 'id' parameter is already fully documented, establishing the baseline of 3. The description adds no format hints (e.g., that the numeric ID is passed as a string) or validity constraints beyond what the schema states.

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 uses a specific verb and resource ('Get a Hearthstone card by ID') and scopes the result to a single record from the public card library, which implicitly separates it from the list-style siblings hearthstone_cards and hearthstone_card_filters. It does not explicitly name an alternative, so it falls just short of the top mark.

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 can infer this is the lookup-by-identifier path rather than a search or list path. There is no explicit when-to-use, when-not-to-use, or statement of what to do when the ID is unknown or the card does not exist.

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