Skip to main content
Glama

Search the tool catalogue

discover_tool_search
Read-onlyIdempotent

Search the Nexus tool catalogue by keyword to find matching tools before calling them. Ranks name and description matches so you can locate the right smart-home tool quickly.

Instructions

Fuzzy search the Nexus tool catalogue by name and description.

Scores every mounted tool's name + description against query with a BM25-lite ranking (term frequency/inverse document frequency plus a small boost when a query word appears in the tool name itself) and returns the top top_k matches.

Use when: finding the right tool name before calling it, instead of keeping the whole tool surface in working memory. Not for: a single tool's full documentation once you have its name — use discover_get_tool_doc. Returns: list of {"name", "namespace", "summary", "score", "access"} dicts, highest score first; empty list if nothing scores above zero. access is "read", "write" or "destructive" (ADR-0002/0003 annotation class).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text search query, e.g. 'turn on light' or 'backup'.
top_kNoMaximum number of ranked hits to return, e.g. 10.
namespaceNoRestrict results to one namespace, e.g. 'card_builder'. Omit to search every namespace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.1
    • addedInput schema / properties / namespace / description
      Added value: +"Restrict results to one namespace, e.g. 'card_builder'. Omit to search every namespace."
    • addedInput schema / properties / query / description
      Added value: +"Free-text search query, e.g. 'turn on light' or 'backup'."
    • addedInput schema / properties / top_k / description
      Added value: +"Maximum number of ranked hits to return, e.g. 10."
  2. Addedv0.18.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnly/idempotent safety profile (lowering the bar), but the description goes beyond by disclosing the ranking algorithm (BM25-lite with name boost), the return shape including `access` class based on ADR annotations, and empty-list behavior when no match scores above zero. This is rich behavioral context an agent needs to interpret results.

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?

Front-loaded with core purpose, then algorithm detail, then usage routing, then return format. Each sentence adds distinct value; no filler or repetition of the schema.

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?

With annotations covering safety, a complete input schema, and an output schema present, the description still discloses the ranking method, the exact return fields, and the empty-list case, fully equipping the agent to call and interpret the tool. Nothing needed for correct invocation is missing.

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% with descriptions for all three params, so the schema already documents query, top_k, and namespace. The description references `query` and `top_k` in prose but does not add syntax or format meaning beyond the schema, so baseline 3 is appropriate.

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+resource ('Fuzzy search the Nexus tool catalogue by name and description') and distinguishes from sibling discover_get_tool_doc by naming it. An agent can determine exactly which discover_* tool to use without opening schemas.

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?

Explicit 'Use when: finding the right tool name before calling it' and 'Not for: a single tool's full documentation once you have its name — use `discover_get_tool_doc`.' Both positive selection and exclusion with the named alternative are present.

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