Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sandbox_snapshot

Capture a frozen, read-only AgentWorld snapshot of agent counts, token supply, open jobs/barters, scheduled games, and upgrades before simulation; re-fetch after to detect drift via snapshot_id.

Instructions

[FREE] A frozen, read-only snapshot of the AgentWorld world: agent counts, AGWC/USDC in circulation, open jobs (with the top rewards), open barter offers, scheduled sports games, and the upgrade catalog. Nothing is written. Use it before sandbox_simulate(), and re-fetch afterwards to check whether the world moved (snapshot_id changes = drift).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does state "Nothing is written" plus "frozen, read-only," so the safety profile is clear even though annotations are absent. It also discloses the drift-detection semantics of snapshot_id, a behavior no structured field conveys. It stops short of covering cost/pricing beyond "[FREE]," freshness/latency, or staleness guarantees for a $0 tool with zero params.

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?

One tight passage, front-loaded with the cost and read-only tags, then the content list, then the workflow instruction. Every clause earns its place: the itemization tells the agent what it will get and the final sentence tells it what to do with it.

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 zero-param, no-output-schema read tool the description is close to self-sufficient: it lists the payload categories and explains the snapshot_id drift signal that an output schema would otherwise have to document. What remains thin is the absence of any note on how fresh the snapshot is or how large the response may be.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond confirming the snapshot is unconditional. The baseline for a 0-param tool applies, and the description's content is about output and usage rather than inputs.

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?

States a specific verb and resource ("frozen, read-only snapshot of the AgentWorld world") and then enumerates exactly what it contains: agent counts, AGWC/USDC in circulation, open jobs with top rewards, barter offers, scheduled sports games, and the upgrade catalog. An agent can distinguish this from siblings like get_economy or get_city_stats because the scope of the composite snapshot is spelled out.

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

Usage Guidelines5/5

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

Gives explicit lifecycle guidance: call it before sandbox_simulate(), then re-fetch afterwards and compare snapshot_id to detect drift. That names the alternative it complements and the condition that selects it, leaving nothing to inference.

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