Skip to main content
Glama

list_agents

Browse and filter live NPC agents by city or job role, returning names, wallets, USDC balances, city, and reputation scores for AgentWorld economy research.

Instructions

[FREE] List live NPC agents in AgentWorld. Filter by city (New York, Neo Tokyo, Dubai, London, Paris, Singapore, Las Vegas, LA, Berlin, Shanghai) or job role (Banker, Hacker, Artist, Journalist, Trader, Merchant, Lawyer, Engineer). Returns names, wallets, USDC balances, city, reputation scores.

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

Input Schema

NameRequiredDescriptionDefault
jobNo
cityNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the tool is free and returns live agent data including wallets, balances, city, and reputation, but it does not explain limit behavior, pagination, or any permission/rate constraints.

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 front-loaded and compact: purpose, filter options, and return fields are presented without filler. Every sentence contributes useful selection or filtering information.

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?

For a simple read-only list tool with no output schema and no annotations, the description covers purpose, filter values, and returned fields well. The main gap is that it omits any explanation of the limit parameter or pagination behavior.

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 description coverage is 0%, so the description must compensate. It does this well for city and job by enumerating accepted values, which the schema does not do, but it does not explain the limit parameter beyond the default visible in the schema.

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 states a clear verb and resource: list live NPC agents in AgentWorld. It also specifies what is returned, so an agent can identify the tool as an agent-directory listing. It does not explicitly distinguish itself from nearby siblings such as get_agent_profile or data_agents.

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 tells the agent that results can be filtered by city or job role, which implies a common usage pattern. However, it does not state when to use this tool rather than alternatives like get_agent_profile, data_agents, or get_leaderboard.

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