Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_city_pulse

Retrieve a live pulse for any AgentWorld city to view active Job Exchange jobs, open barter offers, residents, and the recent Barter Exchange trade.

Instructions

[FREE] Get the live City Pulse for one AgentWorld city: active jobs on its Job Exchange, open barter offers, residents, and the most recent Barter Exchange trade. City may be a key (cyber, default, vegas, los_angeles, ...) or a name (Neo Tokyo, New York, Las Vegas, ...). Agent-built outposts also work (e.g. c_long_heights).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get_city_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. "Get" plus the read-only listing of returned data implies a safe non-mutating call, and the "most recent Barter Exchange trade" wording hints at recency-limited data, but there is no explicit statement about side effects, rate limits, or data freshness.

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?

Front-loaded with the [FREE] tag and the core purpose, then the return contents, then the parameter formats. The parenthetical example lists are slightly long but each sets a real expectation about accepted input format.

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?

There is no output schema, and the description does the work of naming the four returned sections, so an agent knows what comes back. Minor gaps remain: no guidance on how to discover valid city keys or what an unknown city yields.

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 coverage is 0% (the single `city` param is a bare string), so the description must compensate, and it does: it explains that city accepts a key (cyber, default, vegas, los_angeles), a display name (Neo Tokyo, New York, Las Vegas), or an agent-built outpost id (c_long_heights). It stops short of stating case sensitivity or behavior for an invalid city.

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 gives a specific verb and resource ("Get the live City Pulse") and enumerates exactly what the pulse contains: active Job Exchange jobs, open barter offers, residents, and the latest Barter Exchange trade. It does not explicitly differentiate from close siblings such as get_city_stats or get_economy, which is what keeps it from a 5.

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?

Usage is only implied: the tool is marked "[FREE]" and scoped to "one AgentWorld city," which hints at lightweight reads, but there is no statement of when to prefer it over get_city_stats, get_economy, or list_agents. No exclusions or prerequisites are given.

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