Skip to main content
Glama

sella

by io.github.sella-network

service_update

Change a service you own. Only the fields you pass change. Set status to paused to stop taking payments without deleting anything, or closed to retire it. Replacing prices retires the old options and mints new ones; charges already settled keep the price they were sold at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
pricesNoReplaces every existing price option. Omit to leave prices untouched.
statusNo
summaryNo
deliveryNoReplaces the whole delivery setup. This is the everyday update for a service whose product changes on a schedule: refresh payload, leave everything else alone.
service_idYes
visibilityNo
deliverableNo

Schema Changelog

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

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing that only passed fields change, that pausing doesn't delete, that replacing prices retires old options and mints new ones, and that settled charges keep their original price. This adds significant behavioral context not visible in the schema or annotations.

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?

The description is three sentences with no fluff, front-loaded with the primary action, and each sentence provides high-value behavioral information. It is concise without sacrificing clarity.

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 an 8-parameter mutation tool with no output schema, the description covers the most consequential behaviors (partial updates, status effects, price handling) and prerequisites (ownership). It omits details like error conditions, exact return values, or permission requirements, but the annotations and schema cover basic safety information, making it fairly complete.

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?

The description adds meaning to the status parameter (paused vs closed) and the prices parameter (replacement semantics, retirement, and charge preservation), which compensates for the low schema description coverage. However, other parameters like visibility, deliverable, and delivery are not explained in the description, leaving some gaps.

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 tool changes an existing service you own, which distinguishes it from service_create, service_list, and service_deliver. The verb 'Change' plus the owned resource makes the purpose specific and unambiguous.

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?

It provides explicit context for using status values (paused to stop payments without deleting, closed to retire) and clarifies partial-update behavior. It doesn't explicitly name when not to use this tool or alternatives, but the usage context is clear enough for an agent to decide.

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

All sella 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

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