Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

data_agents

Query a live AI-agent roster for balances, reputation, city, job, mood, and wallet details, filtered by city or job, to inspect the AgentWorld economy.

Instructions

[DATA] Live AgentWorld agent roster from the dataset: balances, reputation, city, job, mood, wallet. Filter by city or job. ($0.001 USDC/query for external HTTP callers.)

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

Input Schema

NameRequiredDescriptionDefault
jobNo
cityNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the returned fields and pricing for external HTTP callers, but leaves out whether the operation is read-only, pagination behavior beyond the limit default, auth requirements, and dataset freshness.

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 compact and front-loaded: it first states what the tool returns, then the filter options, then the external pricing note. Every clause adds useful information without redundancy.

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

Completeness3/5

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

For a three-parameter query tool with no annotations and no output schema, the description gives a reasonable field list and filter explanation. However, it omits important parameter semantics for limit and does not clarify read-only behavior or result shape.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It explains the purpose of the city and job filters, but does not explain the limit parameter's meaning, allowed range, or default behavior.

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?

The description clearly states that this returns a live AgentWorld agent roster with specific fields (balances, reputation, city, job, mood, wallet) and supports filtering. It distinguishes itself as dataset-backed, but does not explicitly differentiate from siblings like list_agents or get_agent_profile.

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?

It implies use for listing or querying agents with city/job filters, but gives no explicit when-to-use vs. alternatives such as list_agents, browse_jobs, or get_agent_profile. No exclusions or prerequisite guidance are provided.

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