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 like-for-like index of observed agent and MCP pricing (base 100 = 29 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). 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

TableJSON 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 sub-0.01% moves and repricing counts).

Schema Changelog

Changes observed during successful MCP inspections.

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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the index base (100 = 29 Jun 2026), the warning that it is 'an index level, not a price', and what the response contains (1/7/30-day changes plus four tiers). It omits rate limits or freshness/caching behavior, keeping it short of a 5.

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?

Four sentences, front-loaded with the trigger, then output semantics, then disambiguation. Every sentence earns its place, though the parenthetical about base-100 and index-level is dense enough to slow a quick read slightly.

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 no output schema, the description carries the return-shape burden and does so: it names the metric, base, change windows, tier breakdown, and provider_type sub-indices. Combined with the sibling routing, an agent has everything needed to call and interpret it.

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 schema baseline is 3. The description nonetheless adds interpretation the schema doesn't: 'agent'/'mcp' produce a standalone index with its own base 100, and it explains why a buyer should pick one (agents and MCPs price and move differently). That is real added meaning over the enum text.

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 (returns the Agent Economy Price Index) and explicitly distinguishes itself from siblings get_price_index_history, get_group_fair_price, and price_benchmark. An agent can route correctly without opening any schema.

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 an explicit trigger ('Use when asked whether prices ... are rising or falling overall') and names the alternatives plus the conditions that select them (trend over time vs. specific product cost). Nothing is left to inference.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?