RuneScape Wiki MCP Server

Estimate Flip Profit

estimate_flip

Read-onlyIdempotent

Calculate Grand Exchange flip profit after the 2% RS3 sales tax using an item ID or name, with optional buy and sell prices to model your own offers.

Instructions

Estimate Grand Exchange flip profit after the 2% RS3 sales tax for an item, by itemId or name. This is an ESTIMATE ONLY: guide prices lag the live market, buy limits and fill times are not modelled, and actual profit will differ. Pass buyPrice/sellPrice to model your own offers.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Item name (provide itemId or name). Prefer lookup_item for fuzzy search.
`itemId`	No	Grand Exchange item ID (provide itemId or name)
`buyPrice`	No	Buy price per item in coins. Defaults to the current market price.
`quantity`	No	Number of items to flip (default 1)
`sellPrice`	No	Sell price per item in coins. Defaults to the current market price.

Output Schema

TableJSON Schema

Name	Required	Description
`itemId`	Yes
`taxRate`	No
`buyPrice`	Yes	Buy price per item in coins
`itemName`	No
`quantity`	Yes
`totalTax`	No
`marginPct`	No
`netProfit`	Yes
`sellPrice`	Yes	Sell price per item in coins
`taxPerUnit`	No
`assumptions`	No
`grossProfit`	No
`netProfitPerUnit`	No
`breakEvenSellPrice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.1Oct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "description": "Flip estimate after the RS3 2% seller tax. marginPct is null when the buy cost is 0.",
+  "properties": {
+    "assumptions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "breakEvenSellPrice": {
+      "type": "number"
+    },
+    "buyPrice": {
+      "description": "Buy price per item in coins",
+      "type": "number"
+    },
+    "grossProfit": {
+      "type": "number"
+    },
+    "itemId": {
+      "type": "integer"
+    },
+    "itemName": {
+      "type": "string"
+    },
+    "marginPct": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "netProfit": {
+      "type": "number"
+    },
+    "netProfitPerUnit": {
+      "type": "number"
+    },
+    "quantity": {
+      "type": "integer"
+    },
+    "sellPrice": {
+      "description": "Sell price per item in coins",
+      "type": "number"
+    },
+    "taxPerUnit": {
+      "type": "number"
+    },
+    "taxRate": {
+      "type": "number"
+    },
+    "totalTax": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "itemId",
+    "quantity",
+    "buyPrice",
+    "sellPrice",
+    "netProfit"
+  ],
+  "type": "object"
+}

First observedv1.1.0Aug 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses real behavioral limits: guide prices lag the live market, buy limits and fill times are unmodelled, and results will differ from actual profit. That is meaningful caveat context, though it says nothing about precision, time windows, or data freshness beyond the lag warning.

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?

Three tight sentences, front-loaded with what the tool computes and immediately followed by the accuracy caveat and the key optional-parameter usage. No filler.

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 values need no explanation, annotations cover the safety profile, and the description supplies the estimate-only caveat that annotations cannot express. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds the rationale for buyPrice/sellPrice ('to model your own offers') and restates the itemId-or-name selector, clarifying intent rather than just repeating types.

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 precise verb ('Estimate') plus the exact resource and domain ('Grand Exchange flip profit after the 2% RS3 sales tax'), and names both input modes (itemId or name). This is clearly separable from siblings like get_item_price or compare_items, which do not model flip profit.

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?

Tells the agent how to use it ('Pass buyPrice/sellPrice to model your own offers') and implicitly when it applies versus plain price lookups. It lacks an explicit when-not statement (e.g. use get_item_price for raw prices), so it falls short of full routing guidance.

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

Deploy Server