Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cce_market_view

View Compute Credit Exchange market status to track receipt states, epoch baselines, and recent contributions, with vesting after challenge windows.

Instructions

[FREE] Compute Credit Exchange market view: vested/pending/challenged/voided receipt counts, epoch baseline object (seed, welfare frontier from vested-only data), and recent contributions. Receipts-v2: contributions no longer mint instantly; they vest after a challenge window, backed by a 20% stake.

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": "cce_market_view"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does imply a read-only computation ('view', 'compute') and flags zero cost via '[FREE]', and it usefully explains the Receipts-v2 vesting/challenge-window/20%-stake mechanic behind the counts. It does not state permissions, freshness/caching, or any rate/usage limits.

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 return contents are front-loaded in the first sentence and the vesting note follows as supporting context. It is dense but every clause carries information; the vesting sentence is borderline editorial but does explain why counts differ from minted totals.

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?

The description compensates for the absence of both an output schema and parameters by enumerating the response components and explaining the epoch baseline concept. Minor gaps remain: the window for 'recent contributions', whether scope is global or per-epoch, and the response format are unstated.

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 for the description to disambiguate; baseline 4 applies. The schema's additionalProperties:false confirms the no-argument contract, which the description does not contradict.

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?

States a specific verb and resource ('Compute Credit Exchange market view') and enumerates what it returns: vested/pending/challenged/voided receipt counts, an epoch baseline object, and recent contributions. It does not, however, differentiate itself from the close sibling get_credit_market_stats, which an agent could easily confuse it with.

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

Usage Guidelines2/5

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

The only usage signal is the '[FREE]' tag, which tells the agent there is no cost but not when to reach for this tool over get_credit_market_stats or get_economy. There are no preconditions, no exclusions, and no named alternative.

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