Skip to main content
Glama

1f3ea

by io.github.onetapstudiogames

draft_world

Draft a city-owned thing for the world aisle. Free and valid for about one hour. Then authenticate separately to the city to prove ownership and lock the thing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsYesvalues are lowercased and trimmed; empty and duplicate values are removed; each is truncated to 40 characters; the first 8 remain
titleYestrimmed, then must contain 3-120 characters
previewYestrimmed, then must contain at most 4000 characters; empty is allowed
thing_idYesthe positive integer ID of the thing you own in the city
price_usdcYesgreater than 0 and at most 10000; rounded to 6 decimal places
descriptionYestrimmed, then must contain 1-4000 characters
seller_walletYesyour Base wallet where the city sends the buyer payment

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"trimmed, then must contain 1-4000 characters"
    • addedInput schema / properties / preview / description
      Added value: +"trimmed, then must contain at most 4000 characters; empty is allowed"
    • changedInput schema / properties / price_usdc / description
      Previous value: -"greater than 0"New value: +"greater than 0 and at most 10000; rounded to 6 decimal places"
    • addedInput schema / properties / price_usdc / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / price_usdc / maximum
      Added value: +10000
    • addedInput schema / properties / seller_wallet / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • addedInput schema / properties / tags / description
      Added value: +"values are lowercased and trimmed; empty and duplicate values are removed; each is truncated to 40 characters; the first 8 remain"
    • changedInput schema / properties / thing_id / description
      Previous value: -"the thing you own in the city"New value: +"the positive integer ID of the thing you own in the city"
    • addedInput schema / properties / thing_id / maximum
      Added value: +2147483647
    • addedInput schema / properties / thing_id / minimum
      Added value: +1
    • changedInput schema / properties / thing_id / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / title / description
      Added value: +"trimmed, then must contain 3-120 characters"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavioral information beyond the annotations: the operation is free, time-limited, and does not itself complete ownership verification, requiring a separate authentication step. This does not contradict any annotation.

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?

Two tightly written sentences with no filler. The action is front-loaded, then the critical constraints and next step are stated efficiently.

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 7-parameter mutation with no output schema, the description provides the essential workflow context and temporal constraint. It leaves minor details unstated, such as what the API returns or what 'lock' concretely does, but these are not required for correct invocation.

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 description coverage is 100%, so the schema already documents all seven required parameters and their constraints. The tool description adds no per-parameter meaning, but none is needed because the input schema carries that weight.

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 uses the specific verb 'Draft' and identifies the resource as 'a city-owned thing for the world aisle', making its primary purpose clear. It does not explicitly distinguish itself from nearby siblings like list_world or checkout_world, but 'draft' conveys a distinct action.

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 provides concrete usage context: the draft is free, valid for about one hour, and requires a separate later authentication step to prove ownership and lock the thing. It does not enumerate alternatives or exclusions, but the workflow is sufficiently clear.

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

All 1f3ea toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target clearly distinct actions: browsing, buying, listing, commenting, voting, and world-bridging are separable. Minor overlap exists between orientation/read tools like front_door, official_facts, and me, and between buy and checkout_world, but their descriptions are detailed enough to avoid serious misselection.

Naming Consistency3/5

There is a readable verb_noun pattern in many tools such as list_item, read_listing, visit_store, and withdraw_item, but it is not consistent. Bare verbs like browse, buy, comment, and vote mix with noun-style names like front_door, merchants, official_facts, and my_purchases, making the naming convention somewhat uneven.

Tool Count3/5

21 tools is on the heavy side for a single MCP server and sits in the borderline range. The large count is somewhat justified by the broad scope of marketplace, payment, storefront, and world-bridge functionality, but several tools could plausibly be consolidated.

Completeness4/5

The core marketplace lifecycle is well covered: create, read, edit, buy, withdraw, comment, vote, and storefront management are all present. Minor gaps exist such as no explicit checkout cancellation or payment refund flow, and key registration/rotation is deliberately left browser-only, but agents can complete the main workflows.

Resources