Skip to main content
Glama
Sign In

ArcaneMetriX

by com.arcanemetrix.api
OverviewDiscussionsAdmin

Suggest cards

suggest_cards
Read-onlyIdempotent

Up to ten cards to add to a Commander decklist, ranked, each with the reason, built toward a bracket when one is given.

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": {
      "decklist": "<decklist>"
    },
    "name": "suggest_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
bracketNoThe bracket to build toward; the deck's own when absent.
decklistYesOne card per line (`1 Sol Ring`), at most 250 distinct cards and 20,000 characters. A `Commander` heading or `*CMDR*` marks the commanders.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add shape. It does: the output is capped at ten cards, ranked, and each carries a stated reason, plus bracket-conditioned behavior. It does not say what happens on a malformed or oversized decklist.

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?

A single front-loaded sentence with no filler, and the cap, ranking, and rationale are stated before the optional bracket condition. The phrasing is slightly compressed ('built toward a bracket when one is given') 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?

With no output schema, the description carries the return-shape burden and does so adequately: a ranked list of at most ten cards with reasons. For a one-required-parameter read-only tool this is nearly complete; only error/edge behavior is unstated.

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 67% and both 'decklist' and 'bracket' are documented in the schema, including the fallback to the deck's own bracket. The description only reinforces the 'limit' maximum of ten ('up to ten cards'), adding little meaning beyond the structured fields.

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: it returns up to ten ranked card suggestions for a Commander decklist, each with a reason. That is clearly distinguishable from lookup or analysis siblings, though it never explicitly names or contrasts them.

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 implied by the resource ('to add to a Commander decklist') and the conditional bracket handling ('built toward a bracket when one is given'), but there is no explicit when-to-use or when-not-to-use guidance versus siblings like card_synergy or analyze_my_deck.

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