Skip to main content
Glama

Nevermined Catalog

by io.github.nevermined-io
OverviewDiscussionsAdmin

Search services

search_services

Search the Nevermined Agent Services Catalog for paid services, ranked by ARD HYBRID relevance — semantic (meaning) matches merged with lexical (keyword) matches, most relevant first — falling back to pure lexical when the embedding provider is unavailable. Each result includes a closed matchReason, a per-item rankingSource, and one scale-specific score. A query is required; the other filters are optional. Returns matching listings (vendor, protocol, price label, endpoint). Only the first page is returned: the pageToken in the result cannot be passed back to this tool, so to see other matches narrow the query or filters, or raise pageSize (up to 100). Discovery only; no payment. To have the platform PICK (and optionally pay) the single best service for a need instead of choosing yourself, use route_by_intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoRestrict to services carrying this catalog tag (e.g. a protocol or domain keyword from a listing's `tags`). Combined with `category` it widens the match to either value rather than narrowing it.
queryYesWhat you need, in plain language. REQUIRED. Ranked semantically AND lexically (hybrid), most relevant first — a query describing the need ("translate documents to German") matches on meaning, not only exact words, and also keyword-matches title, descriptions and tags. Falls back to keyword-only ranking when the embedding provider is unavailable.
preferNoMove this opaque catalog slug to the front when it matched the returned page; if it did not match, keep the normal ranked fallback.
excludeNoNever return this opaque catalog slug in the result page.
categoryNoRestrict to services carrying this catalog tag — it filters on tags exactly like `tag`. The category names `list_categories` returns are not stored as tags, so passing one here matches nothing; put a category name in `query` instead. Given together, `category` and `tag` match a service carrying either one.
pageSizeNoPage size, 1–100 (a size of 0 is meaningless and is rejected).
protocolNoRestrict to a payment protocol. Only x402 and mpp are payable via the Router.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / exclude
      Added value: +{
+  "description": "Never return this opaque catalog slug in the result page.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / prefer
      Added value: +{
+  "description": "Move this opaque catalog slug to the front when it matched the returned page; if it did not match, keep the normal ranked fallback.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses hybrid ranking, the lexical fallback when embeddings are unavailable, the result shape (matchReason, rankingSource, one scale-specific score), and a real limitation (only the first page; pageToken cannot be passed back). It does not address auth, rate limits, or cost/auth prerequisites for catalog access, leaving that gap.

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?

Front-loaded with the core behavior and then the pagination constraint and sibling routing, with no wasted sentences. It is somewhat dense with internal jargon (ARD HYBRID, matchReason, rankingSource) that lengthens the prose without helping an agent decide whether to call it.

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

Completeness5/5

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

There is no output schema, so the description must describe returns — and it does (vendor, protocol, price label, endpoint, plus ranking metadata). Combined with the ranking fallback and single-page limitation, an agent has everything needed to call and interpret this correctly.

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 seven parameters including the tag/category OR-widening quirk and the protocol enum. The description mostly restates (query required, pageSize up to 100) rather than adding new semantics, so the baseline of 3 applies.

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?

Names a specific verb and resource (search the Nevermined Agent Services Catalog for paid services) and scopes it as discovery-only. It explicitly distinguishes itself from the sibling route_by_intent, which PICKs/pays instead of letting the caller choose.

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?

States the required input and that all other filters are optional, gives the explicit alternative ('use route_by_intent' when you want the platform to pick and pay), and explains the pagination workaround (narrow the query or raise pageSize) because pageToken cannot be reused. When-to-use and when-not-to-use are both covered.

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

All Nevermined Catalog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources