Skip to main content
Glama

query

Search the qmx knowledge base semantically and by keyword to retrieve ranked code, doc, chat, and learning snippets with file paths and line ranges.

Instructions

Semantic + keyword search over the qmx knowledge base (code, docs, chats, learnings).

    Returns ranked hits with ``path``, ``start_line``/``end_line``, ``symbol``, ``score`` and a
    text snippet. Optional ``kind`` filters to ``code`` | ``doc`` | ``chat`` | ``learning`` |
    ``meeting``.
    

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

Input Schema

NameRequiredDescriptionDefault
kNo
kindNo
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the return shape (ranked hits with path, line range, symbol, score, snippet). It does not state that this is a non-mutating read, how ranking blends semantic and keyword results, how many hits k yields by default, or whether index freshness affects results.

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?

The purpose is front-loaded in the first sentence and the rest is compact. Enumerating return fields is somewhat wasted since an output schema exists, but it is short enough that it does not materially bloat the definition.

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 description covers purpose, corpus, kind values and result shape, which is a reasonable baseline. Against 0% schema coverage and zero annotations, it leaves gaps on the k parameter's meaning and on routing between this tool and the more specific siblings, so an agent could pick or configure it incorrectly.

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 0% and the schema defines kind only as an unconstrained string, so the description adds real value by enumerating code | doc | chat | learning | meeting. However, k is never explained in either the schema or the description, leaving one of three parameters with no documented meaning.

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 names a specific verb and resource: semantic + keyword search over the qmx knowledge base spanning code, docs, chats and learnings. It is clear what the tool does and what content it covers, but it never compares itself to siblings like search_code or recall, so the agent must infer that query is for cross-domain retrieval.

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?

Usage is implied by the corpus list and the kind filter, which tells the agent this is the broad retrieval entry point. There is no explicit when-to-use or when-not-to-use guidance versus search_code, lessons, or recall, and no statement about when the semantic vs keyword path is preferred.

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