rootvine-mcp

Game prices (coming soon)

resolve_game

Read-only

Where to buy a video game. Not live yet: every call returns an explicit "coming soon" — no links, no prices — and contacts no store. Tell the user plainly that games aren't supported yet; never guess a store link or a price. For music, use resolve_music. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`.
`query`	No	The game's name in plain words: 'Elden Ring'.

Output Schema

TableJSON Schema

Name	Required	Description
`live`	Yes	false: games are not live yet — there are no links or prices to give
`query`	Yes
`status`	Yes
`message`	Yes
`results`	Yes
`resolved_at`	Yes
`response_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 26, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "The game's name in plain words: 'Elden Ring'.",
+  "maxLength": 500,
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"The game slug. Format: game-title (lowercase, hyphenated). Example: 'elden-ring'"New value: +"Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`."

addedInput schema / properties / slug / maxLength
```
Added value: +500
```
removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "live": {
+      "description": "false: games are not live yet — there are no links or prices to give",
+      "type": "boolean"
+    },
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query": {
+      "type": "string"
+    },
+    "resolved_at": {
+      "type": "string"
+    },
+    "response_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "availability": {
+            "enum": [
+              "in_stock",
+              "preorder",
+              "available",
+              "unknown"
+            ],
+            "type": "string"
+          },
+          "click_url": {
+            "description": "The link to give the user",
+            "type": "string"
+          },
+          "edition": {
+            "type": "string"
+          },
+          "merchant": {
+            "type": "string"
+          },
+          "merchant_id": {
+            "type": "string"
+          },
+          "price": {
+            "anyOf": [
+              {
+                "additionalProperties": {},
+                "properties": {
+                  "amount": {
+                    "type": "number"
+                  },
+                  "currency": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "amount",
+                  "currency"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "null when no price is listed — never zero, never free"
+          },
+          "price_freshness": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "ranking_reason": {
+            "additionalProperties": {},
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "summary": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "summary"
+            ],
+            "type": "object"
+          },
+          "trust_tier": {
+            "enum": [
+              "authoritative",
+              "verified",
+              "listed"
+            ],
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "purchase",
+              "stream",
+              "subscription"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "rank",
+          "merchant",
+          "merchant_id",
+          "type",
+          "trust_tier",
+          "availability",
+          "price",
+          "click_url",
+          "url",
+          "ranking_reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "enum": [
+        "coming_soon",
+        "success",
+        "partial",
+        "no_results"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "live",
+    "query",
+    "message",
+    "results",
+    "response_id",
+    "resolved_at"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses key behaviors beyond the annotations: it states every call returns an explicit 'coming soon' with no links/prices and no store contact; it adds the 'RootVine never fabricates' truthfulness guarantee; and it explains the UK/GBP scope and error-response expectations. Annotations only say readOnlyHint and openWorldHint, so the description carries significant extra behavioral context with no contradiction.

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?

The description is reasonably concise and front-loaded with purpose and status. There is slight redundancy ('not live yet' appears three times, and 'never guess' appears twice), but overall each sentence contributes meaningful guidance. It earns a 4 rather than a 5 due to minor 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?

For a stub tool with an output schema, the description is notably complete. It covers the tool's current status, user-interaction expectations, limitations (UK-focused, GBP), error-handling behavior, and sibling routing. There is no significant missing information an agent would need to call or respond 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 coverage is 100%, with both parameters (slug and query) already described in the schema. The description does not add any new parameter-specific information beyond what the schema provides, so the baseline score of 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?

The description opens with 'Where to buy a video game', a specific verb+resource statement. It immediately distinguishes itself from resolve_music ('For music, use resolve_music') and explicitly notes the tool is not live yet, so an agent knows exactly what this tool is (or will be) for and how it differs from siblings.

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?

The description gives explicit guidance: 'Not live yet' tells the agent not to expect real results; 'For music, use resolve_music' names the specific alternative; and it provides direct instructions for handling partial and no_results responses ('say which sources didn't answer', 'never fall back to guessing a link'). This is comprehensive usage direction.

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

All rootvine-mcp 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.