Skip to main content
Glama
Sign In

ArcaneMetriX

by com.arcanemetrix.api
OverviewDiscussionsAdmin

Check my collection

check_my_collection
Read-onlyIdempotent

How many copies of each card the user owns in their ArcaneMetriX collection (needs their PRO membership and collection:read). Takes up to 100 card names or oracle ids.

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": {
      "cards": "<cards>"
    },
    "name": "check_my_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesCard names or oracle ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the required PRO membership and collection:read scope, plus the 100-item batch ceiling.

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?

One efficient sentence with purpose front-loaded and prerequisites trailing. Slightly compressed parenthetical phrasing, but nothing is wasted.

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?

No output schema exists, yet the description conveys the return shape (a count per requested card) and covers auth and batch limits. Enough for an agent to call it correctly without guessing.

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% and the single parameter already documents card names or oracle ids, so the baseline is 3. The description's 'up to 100 card names or oracle ids' restates the schema's maxItems and item description rather than adding new meaning.

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?

States a specific verb-and-resource: returns owned copy counts from the user's ArcaneMetriX collection. This is clearly distinct from card lookup or deck tools, though it doesn't explicitly name a sibling to steer against.

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?

Gives prerequisites (PRO membership, collection:read) but no explicit when-to-use versus when-not guidance, and it never names an alternative such as card_lookup for users who just want card data.

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

All ArcaneMetriX 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