Agentery

Get price index

get_price_index

Read-only

Use when asked whether prices of AI agents, tools or MCP servers are rising or falling overall. Returns the current Agent Economy Price Index (AEPI), a chained quoted-price index of observed agent and MCP pricing in US dollars (changes in the publicly quoted price of the same product and offer; base 100 = 30 Jun 2026; an index level, not a price), with 1-, 7- and 30-day change, plus the same for the four buyer tiers (Individual, Pro, Team/SME, Enterprise). Every response names its release_id, reference_currency and methodology_revision; response_mode=full adds fx_attribution (exact native-price and exchange-rate contributions per window: log changes add, level factors multiply) and currency_evidence. provider_type=agent|mcp gives the standalone index for that delivery type; tier narrows to one tier. For the trend over time use get_price_index_history; for what a particular kind of product costs use get_group_fair_price or price_benchmark.

Input Schema

Name	Required	Description
`tier`	No	Filter to one buyer tier ('team' = Team/SME). Default 'all'.
`benchmark_id`	No	Optional: a private custom benchmark token (cb_…) from create_custom_benchmark — returns that cohort's current index instead of the economy index. Cannot be combined with niche.
`provider_type`	No	'all' (default) = the combined whole-economy index; 'agent' or 'mcp' = the standalone index over just that delivery type (own base 100); 'payg' = the standalone pay-as-you-go sub-index (usage rates purchasable without a subscription, engine v2). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index.
`response_mode`	No	'summary' (default) or 'full' (adds exact native / FX / combined contributions for the 1d, 7d and 30d windows with their from/to days and units, the currency-evidence split of the index weight, and the full methodology revision note).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / response_mode / description

Previous value: -"'summary' (default) or 'full' (adds exact sub-0.01% moves and repricing counts)."New value: +"'summary' (default) or 'full' (adds exact native / FX / combined contributions for the 1d, 7d and 30d windows with their from/to days and units, the currency-evidence split of the index weight, and the full methodology revision note)."

Changed1 schema field changedOct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "JSON result; identical to the text content block.",
+  "type": "object"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / provider_type / enum

Previous value: -[
-  "all",
-  "agent",
-  "mcp",
-  "payg"
-]New value: +[
+  "all",
+  "agent",
+  "mcp",
+  "subscription",
+  "hybrid",
+  "one_off",
+  "payg"
+]

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / provider_type / description

Previous value: -"'all' (default) = the combined whole-economy index; 'agent' or 'mcp' = the standalone index over just that delivery type (own base 100). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index."New value: +"'all' (default) = the combined whole-economy index; 'agent' or 'mcp' = the standalone index over just that delivery type (own base 100); 'payg' = the standalone pay-as-you-go sub-index (usage rates purchasable without a subscription, engine v2). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index."

changedInput schema / properties / provider_type / enum

Previous value: -[
-  "all",
-  "agent",
-  "mcp"
-]New value: +[
+  "all",
+  "agent",
+  "mcp",
+  "payg"
+]

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / benchmark_id

Added value: +{
+  "description": "Optional: a private custom benchmark token (cb_…) from create_custom_benchmark — returns that cohort's current index instead of the economy index. Cannot be combined with niche.",
+  "type": "string"
+}

changedInput schema / properties / provider_type / enum

Previous value: -[
-  "all",
-  "provider",
-  "mcp"
-]New value: +[
+  "all",
+  "agent",
+  "mcp"
+]

Changed4 schema fields changedAug 17, 2026

removedInput schema / properties / niche

Removed value: -{
-  "description": "For scope 'niche': a canonical niche slug (e.g. 'customer-support-tier1') or a natural-language task/query (e.g. 'customer support providers'), resolved by the niche resolver.",
-  "type": "string"
-}

changedInput schema / properties / provider_type / description

Previous value: -"Delivery-type scope for scope 'aepi': 'all' (default) = the combined index; 'agent' or 'mcp' = the standalone index over just that provider type (own base 100). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index. Per-type NICHE indices are a Phase-2 follow-up; on scope 'niche' this is acknowledged in the response, not silently applied."New value: +"'all' (default) = the combined whole-economy index; 'agent' or 'mcp' = the standalone index over just that delivery type (own base 100). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index."

changedInput schema / properties / response_mode / description

Previous value: -"'summary' (default) or 'full' (adds exact sub-0.01% moves, per-tier niche detail and repricing counts)."New value: +"'summary' (default) or 'full' (adds exact sub-0.01% moves and repricing counts)."

removedInput schema / properties / scope

Removed value: -{
-  "description": "'aepi' (default) = whole-economy headline + the four buyer tiers; 'niche' = one niche's index.",
-  "enum": [
-    "aepi",
-    "niche"
-  ],
-  "type": "string"
-}

Changed2 schema fields changedAug 1, 2026

changedInput schema / properties / niche / description

Previous value: -"For scope 'niche': a canonical niche slug (e.g. 'customer-support-tier1') or a natural-language task/query (e.g. 'customer support agents'), resolved by the niche resolver."New value: +"For scope 'niche': a canonical niche slug (e.g. 'customer-support-tier1') or a natural-language task/query (e.g. 'customer support providers'), resolved by the niche resolver."

changedInput schema / properties / provider_type / enum

Previous value: -[
-  "all",
-  "agent",
-  "mcp"
-]New value: +[
+  "all",
+  "provider",
+  "mcp"
+]

Changed1 schema field changedJul 31, 2026

addedInput schema / properties / provider_type

Added value: +{
+  "description": "Delivery-type scope for scope 'aepi': 'all' (default) = the combined index; 'agent' or 'mcp' = the standalone index over just that provider type (own base 100). Agents and MCPs price and move differently, so an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index. Per-type NICHE indices are a Phase-2 follow-up; on scope 'niche' this is acknowledged in the response, not silently applied.",
+  "enum": [
+    "all",
+    "agent",
+    "mcp"
+  ],
+  "type": "string"
+}

AddedJul 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the read-only/safe profile, and the description goes well beyond them: it defines the index as a chained quoted-price index (base 100 = 30 Jun 2026, an index level rather than a price) and states every response carries release_id, reference_currency and methodology_revision. It also discloses what response_mode=full unlocks (fx_attribution, currency_evidence), which the agent would otherwise only discover by calling.

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 trigger and the definition are front-loaded, and the closing routing sentence earns its place. The middle is one very long sentence with nested parentheticals (base 100, index level, log changes add / level factors multiply), which is dense but nearly all substantive rather than 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?

Given an output schema exists, the definition covers everything an agent needs to select and call correctly: trigger, index semantics, segment selection, response_mode effect, and sibling routing. Nothing material is left ambiguous.

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 already 100%, and the description still adds meaning: provider_type values are explained semantically ('standalone index over just that delivery type, own base 100') rather than just enumerated, and response_mode's added payload is spelled out. The benchmark_id guidance mentions a 'niche' parameter not present in the schema, which is a small inconsistency but does not obscure usage.

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 resource and scope: the Agent Economy Price Index with 1-, 7- and 30-day change and four buyer tiers. It explicitly distinguishes itself from get_price_index_history (trend over time), get_group_fair_price and price_benchmark (what a product costs), so an agent can separate it from siblings without reading schemas.

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 a concrete trigger ('Use when asked whether prices ... are rising or falling overall') and names the correct alternatives for adjacent questions. It also advises which index segment to read ('an MCP buyer should read the mcp index and an agent buyer the agent index'), which is a routing decision not obvious from the schema.

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

All Agentery tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?