Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

catalog_search

Read-only

Search reviewed sources by query and filters to get bounded metadata and source IDs for explicit selection; detailed records stay linked, not inlined.

Instructions

Search reviewed sources with bounded metadata only. Read known source IDs from simscene://catalog/sources or simscene catalog sources; copy those IDs into filters.source_ids for explicit selection. Detailed records are linked, not inlined.

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": {
      "query": "<query>"
    },
    "name": "catalog_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds useful behavior: results are bounded metadata only, detailed records are linked rather than inlined, and reviewed sources are the target. It does not discuss pagination despite the cursor parameter, but the added output-scope context is substantive.

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?

The description is three sentences with no wasted wording, front-loads the core purpose, and then adds the source-selection workflow and output caveat in a logical order.

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?

The definition adequately covers purpose and output scope for a search tool, and it explains one important filter usage. But with no output schema, 0% schema description coverage, and standard-but-undocumented query/limit/cursor behavior, an agent still lacks enough detail to use all parameters confidently.

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%, so the description must compensate for undocumented parameters. It explains only a hidden path, filters.source_ids, for explicit source selection, and says nothing about the required query, limit, cursor, or the full shape of filters, leaving most parameter meaning unstated.

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 reviewed sources, with the scope limited to bounded metadata. It clearly explains that detailed records are not returned inline, but it does not explicitly distinguish this tool from the sibling catalog_discover.

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

Usage Guidelines3/5

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

It gives a concrete workflow for explicit source selection: read known source IDs from the catalog URI or CLI, then copy them into filters.source_ids. However, it does not say when to use catalog_search instead of catalog_discover or asset_search, and it provides no exclusion guidance.

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