sella

policy_set

Update the purchasing policy for your account. Only the fields you pass change; the rest are unchanged. Tightening limits takes effect immediately for discovery filtering and purchase gating. commerceMode=human_assisted routes paid purchases through operator approval.

Input Schema

TableJSON Schema

Name	Required	Description
`buytemp`	No	Exploration appetite 0 to 1; below 0.5 enables the synthetic-data block.
`agentType`	No
`temporalEnd`	No	Latest acceptable data year.
`commerceMode`	No
`temporalStart`	No	Earliest acceptable data year.
`requiredFields`	No	Fields a dataset must expose.
`dailySpendLimit`	No	Daily spend cap in USDC.
`monthlySpendLimit`	No	Monthly spend cap in USDC.
`maxSpendPerDataset`	No	Per-item cap in USDC.
`highValueEscalationUSDC`	No	Purchases at or above this escalate for approval.
`blockSyntheticBelowBuytemp`	No

Schema Changelog

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

First observedJul 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds valuable context: partial update semantics, immediate effect for tightening, and commerceMode routing for human-assisted purchases. No contradictions with 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?

Three concise sentences with no extraneous information. Each sentence adds distinct value: update behavior, partial updates, and special effects.

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 no output schema and 11 parameters, the description covers the core update behavior and key behavioral nuances. Could mention return value or more parameter context, but it is adequate for an update tool.

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 73%, so many parameters are already documented. The description adds meaning for commerceMode by explaining 'human_assisted' but does not elaborate on other parameters beyond the schema.

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 'Update the purchasing policy for your account' with a specific verb and resource. It distinguishes itself from sibling tools like policy_check and policy_get by focusing on updates.

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?

Provides guidance on partial updates ('Only the fields you pass change') and immediate effects for tightening limits and commerceMode behavior. However, lacks explicit when-not-to-use or alternatives like policy_get for reading.

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?