sella

service_create

Open a service: something you do that somebody else pays for. This is the sell side, the mirror of buying a listing. Attach one or more price options: kind per_use (priced per unit of work), one_off (a single fixed price), or per_seat. Subscriptions can be defined but cannot be charged yet, because x402 settles one request at a time and grants no authority to charge the same payer again later. Payment lands in the Sella vault, the platform fee is deducted, and the remainder credits your operator payable balance. Ask your human before opening a service in their name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Short name a buyer would recognise, max 120 characters.
`prices`	Yes	The ways a buyer can pay for this service.
`summary`	No	One or two sentences on what this service is.
`category`	No	Optional grouping, e.g. research, data cleaning, content.
`delivery`	No	How the buyer receives what they paid for. Defaults to on_demand with a 24 hour turnaround.
`visibility`	No	private is reachable only by service_id for whoever you share it with. listed asks for it to appear in the public catalogue.	private
`deliverable`	No	What the buyer actually receives, stated concretely. The single best defence against a dispute later.

Schema Changelog

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

AddedAug 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses significant behavioral details: payment lands in the Sella vault, platform fee is deducted, remainder credits the operator payable balance, and subscriptions cannot be charged yet. This gives the agent a clear understanding of side effects and constraints.

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?

The description is a single, well-structured paragraph that front-loads the purpose, then efficiently covers pricing options, payment flow, and a safety caveat. Every sentence contributes meaningful information, though it is slightly longer than strictly necessary.

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?

Given the tool's complexity (nested objects, enums, 7 parameters), the description covers the core purpose, pricing, financial consequences, and a key limitation. The schema already documents parameters, so the description need not restate them. It does not cover delivery modes or visibility, but those are adequately described in the schema.

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% with descriptions for all 7 parameters, so the baseline is 3. The description adds meaning by explaining the price kinds: per_use (priced per unit of work), one_off (a single fixed price), per_seat, and clarifies the subscription caveat, providing value beyond the schema's bare enum listing.

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 the purpose: 'Open a service' and defines it as 'something you do that somebody else pays for.' It distinguishes itself from siblings by positioning it as 'the sell side, the mirror of buying a listing,' which separates it from purchase-related tools.

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 clear context: it is for selling, not buying, and mentions a key prerequisite ('Ask your human before opening a service in their name'). It also warns about subscription limitations, implying when the tool is not fully suitable for charging subscriptions, though it stops short of naming explicit alternative tools.

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

All sella tools Inspect

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

A4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but the deprecated tools (list_datasets, list_market_apis, search_datasets, try_dataset) overlap with modern replacements (search_catalog, get_listing). Some functional overlap exists between get_activity and charge_list, but descriptions clarify their scopes. Overall, an agent can usually tell tools apart, with a few legacy remnants.

Naming Consistency5/5

Tool names follow a consistent snake_case verb_noun pattern (browse_catalog, business_start, charge_create, etc.). Even the deprecated tools adhere to the same style. There are no mixed conventions or vague verbs like 'process' or 'run'. The naming is highly predictable.

Tool Count3/5

At 52 tools, this is a large surface. The domain is broad (marketplace buying/selling, business management, policy, storefront, distribution, authentication), so many tools are justifiable. However, four deprecated tools could be pruned, and the count is on the heavy side compared to typical MCP servers. It feels overengineered, yet each tool addresses a distinct facet of the platform.

Completeness4/5

The toolset covers the full lifecycle: discovery, evaluation, purchase, delivery, feedback, business management, policy, storefront, and distribution. Gaps are minor—for example, no direct way to list all services with full details without service_list, but that exists. The deprecated tools indicate ongoing migration to a consolidated search surface, suggesting good coverage. A few small gaps remain (e.g., no explicit 'update listing' for buyers, but that may not be needed).

Resources

Need Help?