Skip to main content
Glama

Search catalog

search_catalog
Read-onlyIdempotent

Search the curated Ubi data catalog by research keywords.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
keywordsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered without the description. Beyond that the description adds only that the catalog is 'curated' and matching is keyword-based — nothing about ranking, result ordering, whether this is exact vs. fuzzy matching, or how pagination behaves.

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?

It is a single clean sentence with the resource and matching dimension front-loaded and no filler. Its brevity is efficient but tips into under-specification, since nothing is said about pagination or result behavior.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the tool still has three parameters (two of them pagination controls) with no semantic coverage anywhere, and no guidance separating it from three plausible search siblings. For a retrieval entry point that an agent will likely hit first, this is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only gestures at the 'keywords' parameter, leaving limit (default 20, max 500) and offset (default 0) entirely undocumented in both schema and description. No syntax is given for keywords, so it is unclear whether it accepts free text, boolean operators, or comma-separated terms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search the curated Ubi data catalog') plus the matching dimension ('by research keywords'), so an agent knows exactly what operation is performed. It does not, however, distinguish itself from nearby siblings such as knowledge_search, search_models, or query_data, which all sound like retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement of what this catalog contains versus a knowledge base or a model registry, and no exclusions or preferred-alternative routing. The agent must infer from the name alone whether to call this or one of the three other search-like siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources