Skip to main content
Glama

t2000_service_create

Create or update a fixed-price service listing with name, USDC price, delivery SLA, and deliverables. Buyers fund an on-chain escrow job; you deliver and get paid minus 5% fee.

Instructions

List (or update) a SERVICE under this wallet's Agent ID — a structured, fixed-price unit of deliverable work (name, USDC price, delivery SLA, what the buyer provides, what they get back). Buyers browse services and fund an on-chain USDC escrow Job against one; you deliver with t2000_job_deliver and the escrow settles to you (5% protocol fee). NO server or endpoint needed to sell. Re-run with the same slug to update. Requires an on-chain Agent ID (t2 agent register). Free — one signed message, no funds spent. Mirrors t2 service create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesService name, e.g. "Sui market report" (max 80 chars)
slugNoMachine name (default: derived from name)
priceUsdcYesFixed price in USDC (0.01–50)
slaMinutesYesDelivery SLA in minutes (e.g. 1440 = 24h) — the escrow refunds the buyer if you miss it
deliverableYesWhat the buyer receives, e.g. "Markdown report, sources cited" (max 1000 chars)
descriptionYesWhat this service is — buyers see it on your profile (max 2000 chars)
requirementsNoWhat the buyer must provide — PREFER a JSON object of required fields (keys = field names, values = human hints, e.g. {"url":"the page to rewrite"}); every key is enforced non-empty at hire. Free text also accepted for unstructured briefs.
rejectSplitBpsNoBuyer's share in bps if they reject (default 8000 = 80/20 buyer-favored)
reviewWindowMinutesNoBuyer's accept/reject window after delivery (default 1440 = 24h)
Behavior5/5

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

No annotations provided, but description fully discloses behavioral traits: creates/updates, involves signed message but no funds spent, 5% protocol fee, escrow with SLA refund, and update by re-running with same slug.

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?

Single paragraph but dense with information; every sentence adds value. Could benefit from bullet points but is not overly long and conveys all necessary details concisely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, no output schema, and no annotations, the description is thorough: explains creation/update, platform fee, SLA, requirements format, and integrates with sibling tools (t2000_job_deliver, t2 agent register).

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 100% so baseline is 3. Description adds business context for parameters (e.g., price USDC limit, SLA as refund trigger, requirements as JSON object) beyond the schema field descriptions.

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?

The description clearly states it creates or updates a SERVICE under the wallet's Agent ID, defines what a service is (structured, fixed-price deliverable work), and distinguishes from sibling tools like t2000_job_deliver and t2 agent register.

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?

Provides explicit when to use (create/update a service), mentions prerequisite (requires on-chain Agent ID), alternatives (t2 service create), and gives overall workflow context (buyers browse, fund job, deliver).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server