Skip to main content
Glama

sella

by io.github.sella-network

search_datasets

Read-only

Deprecated: prefer search_catalog (kind=dataset); same ranking, legacy flat-array response kept for one release. Search the catalogue by keyword and optional filters. Use required_fields to find datasets whose schema contains needed columns before payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNo
limitNoMax items to return (1–100)
queryNoOptional free-text search query across title, description, and tags
formatNo
sort_byNonewest
categoryNoFilter by category
modalityNo
max_price_usdcNoOptional maximum dataset price in USDC
required_fieldsNoOptional structured fields that must exist in the dataset schema

Schema Changelog

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

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true. Description adds life cycle (deprecated, one release), response format (flat-array), and matching ranking. No contradiction. Provides behavioral context beyond annotations.

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?

Two concise sentences: first packs deprecation, alternative, and behavioral note; second states tool purpose and a key use case. Front-loads critical deprecation info. Slightly dense but no wasted words.

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

Completeness3/5

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

Covers deprecation, alternative, and required_fields usage. Lacks detail on other parameters, sorting, or output details beyond flat-array mention. No output schema, so more description could help. Adequate but not fully comprehensive for 9 parameters.

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 56% (5 of 9 params described). Description adds meaning to required_fields by linking to schema-checking before payment, and summarizes optional filters. But does not expand on tier, format, sort_by, modality, or category beyond 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?

Description clearly states deprecation and directs to search_catalog, then specifies it searches catalog by keyword and filters. Distinguishes from siblings by naming the preferred alternative and explaining the legacy flat-array response.

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?

Explicitly says 'prefer search_catalog' for new work and explains the response format difference. Mentions using required_fields for pre-payment schema checks, giving a specific use case. Could more explicitly state when not to use it, but the deprecation notice is sufficient.

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