Skip to main content
Glama
Oolab-labs

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

searchTools

Read-only

Find tools by keyword or category before listing them. In lazy-tools mode, call this first to get schemas inline and avoid extra requests.

Instructions

Find tools by keyword/category before tools/list. In --lazy-tools mode, call this first then tools/schema, or set includeSchema:true to return each match's inputSchema inline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 10, max 50)
queryNoKeyword to match against tool name and description
categoriesNoFilter by categories (e.g. lsp, git, terminal, debug, editor, analysis, github, bridge)
includeSchemaNoInclude each matched tool's inputSchema inline so it can be called without a follow-up tools/schema request (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.3
    • addedInput schema / properties / includeSchema
      Added value: +{
+  "description": "Include each matched tool's inputSchema inline so it can be called without a follow-up tools/schema request (default false).",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds meaningful behavior beyond that: the lazy-mode sequencing and the fact that includeSchema changes whether a second round-trip is needed. It does not cover result ordering, pagination beyond the limit param, or matching semantics (substring vs fuzzy), leaving modest gaps.

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 tightly packed sentences with zero filler, front-loaded with the core purpose and followed by the workflow caveat. Each clause carries information an agent needs.

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?

For a read-only, four-parameter discovery tool with full schema coverage and no output schema, the description covers purpose, routing, and the key mode-dependent workflow. Only the shape of the returned match list and matching semantics are unstated, minor for this tool.

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 coverage is 100%, so every parameter is already documented, including default/max for limit and the effect of includeSchema. The description reinforces includeSchema's purpose but adds no syntax, matching semantics, or category-vs-query interaction beyond what the schema states. Baseline 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?

States a specific verb (find) and resource (tools) with matching dimensions (keyword/category) and anchors it relative to tools/list, which no sibling tool duplicates. An agent can identify this as the discovery/meta-lookup tool without opening the schema.

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?

Gives explicit workflow context: in --lazy-tools mode call this first, then tools/schema, or set includeSchema:true to avoid the follow-up call. It stops short of saying when not to use it (e.g., in normal mode where tools/list already lists everything), so routing is clear but not fully conditioned.

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

Deploy Server

Other Tools