Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Search CLO Python API

clo_search_api
Read-only

Search CLO's Python API reference by keyword to find function signatures, documentation, and option struct types without needing CLO running.

Instructions

Search CLO's Python API reference (read from the installed CLO application) by keyword. Returns matching function signatures with their documentation, and matching option struct types. Works without CLO running.

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": "clo_search_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 12).
queryYesKeywords, e.g. "topstitch", "elastic", "shrinkage", "avatar pose", "graphic".
moduleNoRestrict the search to one module.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real context on top: the data source is the installed CLO application, the payload includes signatures with documentation and option struct types, and no running instance is needed. It stops short of describing result ordering or relevance ranking, which would matter for a keyword search.

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?

Two compact sentences, front-loaded with the action and resource, followed by return content and the offline-capability note. No filler and nothing redundant with the title.

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?

With no output schema, the description correctly accepts the burden of describing returns (signatures plus docs, option struct types), and the environment constraint is stated. Minor gaps remain around result ordering and whether truncation by the default limit of 12 is signalled, but an agent can call this correctly as written.

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%, including a query example and an enumerated module list, so the schema carries the parameter burden. The description adds no extra semantics about query syntax (multi-word, stemming, matching behavior) or how limit interacts with module scoping.

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?

Specific verb+resource: 'Search CLO's Python API reference ... by keyword', plus a precise statement of what comes back (function signatures with docs, option struct types). It is implicitly distinct from the execution-oriented siblings like clo_execute_python, but never names or contrasts with any sibling explicitly.

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?

Provides one genuinely useful usage signal — 'Works without CLO running' — which tells the agent this is safe to call in a disconnected state. However, it gives no guidance on when to prefer this over clo_execute_python or other lookup paths, and no stated workflow such as looking up a signature before executing code.

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