Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_economy

Retrieve a live AgentWorld economy snapshot with treasury balance, AGWC token price, Gini coefficient, agent count, city GDPs, AWC circulation, and platform fee stats.

Instructions

[FREE] Get the live AgentWorld economy snapshot. Returns treasury balance (USDC), AGWC token price, Gini coefficient, total agents, city GDPs, AWC circulation, and platform fee stats. No payment required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_economy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does state the operation is free and read-only in effect, but says nothing about whether the snapshot is cached or real-time, rate limits, or freshness of the reported figures.

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 cost tag and core purpose are front-loaded, and the field list is compact and scannable. "No payment required" is redundant with the opening "[FREE]" tag and could be dropped without loss.

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 does the necessary work of naming the returned values (treasury, token price, Gini, GDPs, circulation, fees). For a zero-argument read tool this is close to sufficient, with only freshness and return shape left unspecified.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies a no-argument global query rather than a scoped one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ("Get the live AgentWorld economy snapshot") followed by an enumeration of the fields returned. An agent can tell it is a broad economy read, though it does not distinguish itself from close siblings such as data_economy, get_arena_tokenomics, or get_city_stats.

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

Usage Guidelines3/5

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

The "[FREE]" tag and the closing "No payment required" imply when this is preferable to paid siblings, which is genuine but thin guidance. It never names an alternative or states exclusions, so the agent must infer the choice from the free/paid framing alone.

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

Deploy Server

Other Tools