Skip to main content
Glama

agentery

by com.agentery
OverviewDiscussionsAdmin

get_price_index

Call this for the CURRENT level of the Agent Economy Price Index (AEPI) — a chained like-for-like index over observed provider/MCP pricing (base 100 = 29 Jun 2026). It is an INDEX LEVEL, not a market price or tradeable asset. Returns the whole-economy headline index level with change_1d/change_7d/change_30d, as_of, like_for_like_pair_count, status and the methodology version, PLUS the same fields for the four buyer tiers (Individual, Pro, Team/SME, Enterprise). provider_type returns the standalone index for one delivery type (provider or mcp, own base 100) — agents and MCPs price and move differently. tier filters to one buyer tier; response_mode 'full' adds exact sub-0.01% moves and repricing counts. Reads the SAME canonical series as the /aepi page, so the MCP and website agree for a given timestamp. (Also accepts a benchmark_id to read a private custom benchmark's current index.) The economy index is whole-market by design — for pricing on a specific capability use market_report or price_benchmark.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoFilter to one buyer tier ('team' = Team/SME). Default 'all'.
benchmark_idNoOptional: 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_typeNo'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_modeNo'summary' (default) or 'full' (adds exact sub-0.01% moves and repricing counts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider_type / enum
      Previous value: -[
-  "all",
-  "agent",
-  "mcp",
-  "payg"
-]New value: +[
+  "all",
+  "agent",
+  "mcp",
+  "subscription",
+  "hybrid",
+  "one_off",
+  "payg"
+]
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed2 schema fields changed
    • 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"
+]
  4. Changed4 schema fields changed
    • 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"
-}
  5. Changed2 schema fields changed
    • 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"
+]
  6. Changed1 schema field changed
    • 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"
+}
  7. Added

TDQS

A4.5/5.0
Behavior4/5

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

There are no annotations, so the description carries full behavioral disclosure. It explains that the tool is read-oriented, returns a whole-economy headline index plus per-tier and per-provider-type series, treats standalone provider_type indices with their own base 100, and reads the same canonical series as the /aepi page so the MCP and website agree. It does not discuss access requirements or rate limits, but for a non-destructive data-read tool the behavioral context is strong.

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 dense but front-loaded with the core purpose ('CURRENT level of AEPI') before diving into output fields and modes. Every sentence carries substantive information, though the return-field enumeration and long parenthetical make it slightly heavy. It is appropriately sized for a tool with four parameters and no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 takes responsibility for explaining return values, and it enumerates the index fields, per-tier fields, provider_type variants, response_mode behavior, benchmark override, and the canonical-series guarantee. It is largely complete for correct invocation, but it does not state output formatting, field nesting, or potential parameter-combination constraints beyond what is implied in the schema.

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 real meaning beyond the schema: response_mode 'full' adds exact sub-0.01% moves and repricing counts, provider_type returns standalone indices with their own base 100, and benchmark_id reads a private custom benchmark's current index. These clarifications help an agent choose parameter values correctly rather than merely knowing they exist.

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 a specific verb and resource: 'Call this for the CURRENT level of the Agent Economy Price Index (AEPI)'. It then disambiguates the tool's domain by stating it returns an index level, not a market price or tradeable asset, and contrasts it with market_report and price_benchmark for capability-level pricing. This makes the tool's purpose and scope unmistakable, even among many 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 explicitly says when to use this tool (current index level), what it is not for ('not a market price or tradeable asset'), and when to use alternatives ('for pricing on a specific capability use market_report or price_benchmark'). It also gives buyer-type guidance, e.g., an MCP buyer should read the 'mcp' index and an agent buyer the 'agent' index. This provides clear operational selection criteria.

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

All agentery toolsInspect
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.

Resources