Skip to main content
Glama
Sign In

CardNexus

by com.cardnexus
OverviewDiscussionsAdmin

Get an inventory summary

get_inventory_summary
Read-onlyIdempotent

Returns the number of inventory lines and cards, how many are listed for sale, the value at market price in EUR and USD, a breakdown by game, and the daily or weekly history of the total value over a chosen period. Lines without a market price count as zero value. Listed cards and the asking value count the full owned quantity of each listed line.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_inventory_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoA game slug; restricts totals and history to it.
detailNo`detailed` adds the listed split, line counts and unpriced cards for every game.concise
periodNoRange of the value history. `none` returns live totals only.30d
granularityNo`daily` for 7d and 30d, `weekly` for 90d and 365d by default; `daily` is refused for 365d.

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 establish that this is a read-only, idempotent, non-destructive operation. The description adds useful semantics beyond annotations: lines without a market price count as zero, and listed cards count the full owned quantity, which materially affects interpretation of the returned value.

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?

The description is two sentences with no wasted text. It front-loads the returned summary components and then adds only the important valuation edge cases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description enumerates the key return components: counts, listed status, EUR/USD value, game breakdown, and value history. Combined with full schema coverage and read-only annotations, it is complete enough for an agent to call the tool correctly.

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 schema already fully documents game, detail, period, and granularity, including enum behavior and defaults. The description reinforces the existence of game breakdown and daily/weekly history but does not add parameter-level meaning beyond the schema.

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 gives a specific verb and resource: returns inventory counts, listed quantities, market value in EUR/USD, game breakdown, and value history. It clearly distinguishes this from item-level inventory tools, though it does not explicitly name sibling alternatives such as search_inventory or get_sales_summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the summary contains but does not state when to use this tool versus alternatives like search_inventory, get_sales_summary, or get_price_history. Usage is only implied by the word 'summary' and the available period/detail parameters.

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

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