Skip to main content
Glama

mmo_economy_dashboard

Retrieve macro-economic data across supported MMOs including inflation rates, currency valuations, RMT indices, market health scores, and cross-game arbitrage signals. Select specific metrics and games.

Instructions

Get a macro-economic dashboard across all supported MMOs. Inflation rates, currency valuations, RMT (real-money trading) indices, market health scores, and cross-game arbitrage signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricNoall
gamesNo
Behavior2/5

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

There are no annotations provided, so the description must disclose behavioral traits. It only lists output items but does not state whether the tool is read-only, has side effects, or requires specific permissions. The agent must assume it is non-destructive, but this is not explicit.

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?

The description is a single concise sentence with a bullet list of outputs. It is front-loaded with the main action ('Get a macro-economic dashboard') and wastes no words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not clarify parameter usage, return format, or typical response structure. For a tool with two parameters and no schema descriptions, more context is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain the two parameters. The 'metric' and 'games' parameters are not described; the listed output items only partially overlap with the metric enum. The agent cannot understand how to use these parameters from the description alone.

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 clearly states the tool's purpose: retrieving a macro-economic dashboard across all supported MMOs. It lists specific metrics (inflation, currency valuations, RMT indices, etc.), distinguishing it from sibling tools like gold conversion or player portfolio by its broad overview nature.

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 description implies usage for obtaining a macro-economic overview, but does not explicitly state when to use this tool versus alternatives. No mention of exclusions or when-not scenarios, leaving the agent to infer based on other tools' names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/mmoagent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server