Midpoint Card Prices

Get card price ladder

get_card_prices

Read-onlyIdempotent

Use this when the user wants the full current value of a specific card: ungraded prices by condition (NM/LP/MP/HP) and graded prices for every company and grade on record (PSA, CGC, BGS, SGC, TAG). Requires a card id from search_cards. Prices are USD market values from real sold listings, refreshed daily. Do not use to search by name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`card_id`	Yes	Catalog card id from search_cards, e.g. "swsh7-215" or "pricecharting-1821843".

Output Schema

TableJSON Schema

Name	Required	Description
`raw`	Yes
`card`	Yes
`links`	Yes
`graded`	Yes
`summary`	Yes
`variant`	Yes	The printing the raw and graded rungs refer to (e.g. "holofoil", "1st edition"). Other printings are listed under other_variants.
`currency`	Yes
`raw_note`	Yes	Set when the raw condition ladder is out of order (thin data): treat raw prices as low confidence.
`captured_on`	Yes	Date of the latest price capture (UTC)
`other_variants`	Yes	Other printings of the same card id (reverse holo, 1st edition…) with their own prices. Never mix these with the main ladder.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 19, 2026

addedOutput schema / properties / other_variants

Added value: +{
+  "description": "Other printings of the same card id (reverse holo, 1st edition…) with their own prices. Never mix these with the main ladder.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "graded": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "company": {
+              "type": "string"
+            },
+            "grade": {
+              "type": "string"
+            },
+            "market_usd": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "company",
+            "grade",
+            "market_usd"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "raw": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "condition": {
+              "type": "string"
+            },
+            "high_usd": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "low_usd": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "market_usd": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "condition",
+            "market_usd",
+            "low_usd",
+            "high_usd"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "variant": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "variant",
+      "raw",
+      "graded"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / raw_note

Added value: +{
+  "description": "Set when the raw condition ladder is out of order (thin data): treat raw prices as low confidence.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / variant

Added value: +{
+  "description": "The printing the raw and graded rungs refer to (e.g. \"holofoil\", \"1st edition\"). Other printings are listed under other_variants.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "card",
-  "currency",
-  "captured_on",
-  "raw",
-  "graded",
-  "summary",
-  "links"
-]New value: +[
+  "card",
+  "currency",
+  "captured_on",
+  "variant",
+  "raw_note",
+  "raw",
+  "graded",
+  "other_variants",
+  "summary",
+  "links"
+]

First observedSep 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds non-redundant context: prices are USD market values from real sold listings and refreshed daily, and the output covers ungraded and graded tiers. No contradiction with annotations.

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?

Four short sentences with the usage instruction front-loaded, followed by prerequisite, data source, and exclusion. No filler or repetition.

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?

With a single well-documented parameter, an output schema, and annotations covering safety, the description supplies the remaining operational context: when to use, prerequisite, data provenance, and an exclusion. Nothing needed for correct invocation is missing.

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 schema description already explains card_id and provides examples ('swsh7-215'). The description repeats the search_cards prerequisite, adding no new semantic information beyond the schema. Baseline 3 is appropriate.

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: 'full current value of a specific card' and enumerates exact output categories (ungraded NM/LP/MP/HP and graded PSA/CGC/BGS/SGC/TAG). The closing instruction 'Do not use to search by name' distinguishes it from search_cards, and the title reinforces the resource. This is more specific than a generic price tool.

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?

Opens with 'Use this when the user wants the full current value of a specific card,' explicitly tying to a user need. It states the prerequisite ('Requires a card id from search_cards') and gives an explicit when-not ('Do not use to search by name'), effectively routing name-based lookups to search_cards. It doesn't name alternatives like get_price_history, but the when/when-not coverage is strong.

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

All Midpoint Card Prices tools Inspect

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.