RuneScape Wiki

Summarize Price History

summarize_price_history

Read-onlyIdempotent

Summarize one item's recent Grand Exchange prices: min, max, average, change, and average daily volume. Pass exactly one of itemId or name, and optional days from 7 to 90 (default 30). Use get_item_graph for the full daily series.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Size of the trailing window in days (7-90, default 30)
`name`	No	Item name (provide itemId or name)
`itemId`	No	Grand Exchange item ID (provide itemId or name)

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Name supplied by the caller, when given
`itemId`	Yes	Grand Exchange item ID
`avgPrice`	Yes	Average price in the window, in coins
`maxPrice`	Yes	Highest price in the window, in coins
`minPrice`	Yes	Lowest price in the window, in coins
`changeAbs`	Yes	latestPrice minus oldestPriceInWindow
`changePct`	Yes	Percent change across the window
`windowDays`	Yes	Trailing window actually summarized
`latestPrice`	Yes	Newest price in the window, in coins
`sampleCount`	Yes	Daily samples inside the window
`avgDailyVolume`	No	Average daily volume, when the source provided it
`oldestPriceInWindow`	Yes	Oldest price in the window, in coins

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "avgDailyVolume": {
+      "description": "Average daily volume, when the source provided it",
+      "type": "number"
+    },
+    "avgPrice": {
+      "description": "Average price in the window, in coins",
+      "type": "number"
+    },
+    "changeAbs": {
+      "description": "latestPrice minus oldestPriceInWindow",
+      "type": "number"
+    },
+    "changePct": {
+      "description": "Percent change across the window",
+      "type": "number"
+    },
+    "itemId": {
+      "description": "Grand Exchange item ID",
+      "type": "integer"
+    },
+    "latestPrice": {
+      "description": "Newest price in the window, in coins",
+      "type": "number"
+    },
+    "maxPrice": {
+      "description": "Highest price in the window, in coins",
+      "type": "number"
+    },
+    "minPrice": {
+      "description": "Lowest price in the window, in coins",
+      "type": "number"
+    },
+    "name": {
+      "description": "Name supplied by the caller, when given",
+      "type": "string"
+    },
+    "oldestPriceInWindow": {
+      "description": "Oldest price in the window, in coins",
+      "type": "number"
+    },
+    "sampleCount": {
+      "description": "Daily samples inside the window",
+      "type": "integer"
+    },
+    "windowDays": {
+      "description": "Trailing window actually summarized",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "itemId",
+    "windowDays",
+    "sampleCount",
+    "latestPrice",
+    "oldestPriceInWindow",
+    "minPrice",
+    "maxPrice",
+    "avgPrice",
+    "changeAbs",
+    "changePct"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the input rule that exactly one of itemId/name must be passed and the window bounds, but says nothing about pagination, rate limits, or data staleness that would go beyond the structured fields.

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?

Two sentences, both front-loaded with the most important information: what is computed first, then the input constraint and the sibling escape hatch. No filler or redundant restatement of the title.

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?

An output schema exists, so return-value detail need not be repeated, and the annotations carry the safety profile. Between the description's metric list, the one-of input rule, the window bounds, and the sibling pointer, an agent has everything needed to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description nonetheless adds value the schema leaves ambiguous: 'Pass exactly one of itemId or name' resolves whether both may be supplied (the schema only says 'provide itemId or name'), and it restates the days range/default for quick reference.

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 (summarize) and resource (one item's recent Grand Exchange prices) and enumerates the computed metrics (min, max, average, change, average daily volume). It also names the sibling get_item_graph and the condition that distinguishes them (full daily series), so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

Gives one explicit alternative and when to prefer it: 'Use get_item_graph for the full daily series.' That is real routing guidance, but it does not address the other plausible siblings (get_item_price, compare_items) or state when a summary is preferable to a raw lookup beyond the series-vs-summary contrast.

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

All RuneScape Wiki 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.