Skip to main content
Glama

sella

by io.github.sella-network

call_api

Destructive

Call one catalogue API endpoint and pay for it. Settles from YOUR agent wallet, not from a Sella balance, so the wallet must hold USDC on a chain the endpoint accepts. Find endpoint_id with browse_catalog or get_listing. Pass dry_run to get the price, the seller, and the policy verdict without calling or paying anything. Endpoints a probe proved unpayable or unreachable are refused before any money moves. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body sent to the upstream endpoint. Check the endpoint inputSchema first; 40 percent of catalogue endpoints publish one.
dry_runNoQuote and policy-check only. Nothing is called and nothing is paid.
endpoint_idYesEndpoint id from browse_catalog (the leaf) or get_listing.
idempotency_keyNoReuse the same key when retrying so a call that already settled is not paid for twice.

Schema Changelog

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

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the destructive/paying nature is disclosed. The description adds valuable context beyond annotations: settlement from agent wallet (not Sella balance), USDC requirement with chain constraints, the dry_run safe-check path, refusal of proven-unpayable endpoints before any money moves, and the authentication requirement. This is rich behavioral disclosure.

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?

Packed but efficient—five sentences each carrying distinct information: the core action, the settlement precondition, how to find the endpoint, the dry_run safety path, and the refusal behavior. Slightly dense but no wasted words.

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 paid mutation tool with no output schema, the description is thorough: it covers preconditions (wallet, USDC, auth), safety escapes (dry_run, refusal before payment), retry semantics (idempotency_key), and reference points (browse_catalog/get_listing). Minor gap: no statement about what the response returns, but absent an output schema definition, the description reasonably focuses on behavioral context.

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 4 parameters well. The description adds some value by explaining the body should reference inputSchema (40% publish one), clarifying idempotency_key's purpose for retry dedup, and confirming dry_run performs no payment. But since the schema already covers these at high detail, the description adds marginal supplementary value.

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 calls one catalogue API endpoint and pays for it, specifying the verb (call), resource (catalogue API endpoint), and key distinguishing behavior (payment from agent wallet). It differentiates from siblings by noting the wallet settlement and the need to find endpoint_id via browse_catalog or get_listing.

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?

The description explicitly tells when to use dry_run for quote-only operations, explains the wallet/USDC settlement precondition, says authentication is required, and references how to find endpoint_id. It gives clear usage context for a paid action, including the idempotency_key for retries, and warns that unpayable endpoints are refused before money moves.

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