Skip to main content
Glama

Sync World

sync_world
DestructiveIdempotent

Read the city public offer and mirror a completed ownership transfer or cancellation into the market. After the city reports claimed, the market independently requires the same Base transfer in its canonical block at or below the finalized head. Its block time must be at or after reserved_at and strictly before reserved_until; finality may be observed later. Pending or temporarily unavailable finality writes no purchase: retry this same sync and do not pay again. Conflicting finalized evidence is preserved as needs_review with no sale; do not pay again, and repeating this sync only rereads that review state. payment_pending remains locked and writes no purchase during at most two hours of automatic city recovery. Canonical finalized invalid evidence becomes payment_invalid; a recovery deadline without an ownership transfer becomes payment_expired; retained payment evidence becomes founder_review. All three close the lane without a sale. Do not pay again; the city seller then authenticates to the city and POSTs {} to the city cancel URL. If the city offer reads phase thing_ended, the thing's end came with no accepted payment evidence: sync records the listing as thing_ended with no sale, cancels its draft, expires open checkouts, and returns city_cancel_url; the city seller POSTs {} to city_cancel_url once no payment window is open. This never takes payment.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "sync_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / listing_id / maximum
      Added value: +2147483647
    • addedInput schema / properties / listing_id / minimum
      Added value: +1
    • changedInput schema / properties / listing_id / type
      Previous value: -"number"New value: +"integer"
  2. Added

TDQS

A3.6/5.0
Behavior5/5

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

Beyond the supplied annotations, the description discloses concrete side effects and state transitions: it writes a purchase only when finalized evidence matches, preserves conflicting evidence as needs_review, cancels drafts, expires open checkouts, and returns city_cancel_url for thing_ended. It also explains idempotent retry behavior and confirms the tool never takes payment, which is exactly the kind of behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded, but the remainder is a dense wall of jargon-heavy clauses with repeated warnings such as 'do not pay again' and no structural grouping of state outcomes. For a complex state machine, the length is somewhat justified, but the presentation makes the content harder to scan than necessary.

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?

The description covers many edge cases and failure states, which is important for this complex tool, and it mentions at least one return value (city_cancel_url). However, with no output schema and no explanation of the sole input parameter, the definition is not fully complete for an agent that must understand both input meaning and the full response shape.

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

Parameters2/5

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

There is one required parameter, listing_id, and schema description coverage is 0%, so the description must carry the burden. It refers repeatedly to 'the listing' and the city offer but never explains what listing_id identifies, how it relates to the city public offer, or what bounds or format are expected beyond the schema's integer type.

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 first sentence states a specific verb and resource: read the city public offer and mirror a completed ownership transfer or cancellation into the market. The purpose is therefore recoverable, but it relies heavily on domain jargon like 'city public offer' and 'market' and does not explicitly distinguish itself from siblings such as cancel_world_draft or checkout_world.

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

Usage Guidelines4/5

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

The description gives clear invocation contexts: sync after the city reports claimed, retry the same sync when finality is pending or temporarily unavailable, and do not pay again in review or locked states. It does not name alternative tools or explicit exclusions, which keeps it below the top score, but the state-specific guidance is substantial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources