Skip to main content
Glama

semantic_search

Search document indexes using semantic vectors or keywords to find relevant passages by meaning or exact terms.

Instructions

Semantic vector or keyword search across document index

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

Input Schema

NameRequiredDescriptionDefault
inputNoOptional input document
limitNoMax results (default 5)
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden and does not. It says nothing about ranking, result format, index scope, permissions, or what happens with the two search modes, which is a substantial gap for a tool with zero annotation coverage.

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?

A single compact phrase with no wasted words, and the resource is front-loaded. Its brevity borders on under-specification rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and three parameters, the definition should do much more work. It omits index scope, result ordering, and mode selection, so an agent cannot confidently predict the tool's behavior from the description alone.

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 baseline is 3, and the description adds nothing beyond the schema. In particular, the odd optional "input" document parameter is left unexplained in both places, and the description could have clarified how it interacts with the query.

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?

States a specific verb (search) plus the resource (document index) and names two modes, semantic vector and keyword. It is clear what the tool does, but it gives no hint of how this index relates to the pdf_search and workspace_search siblings, so scope remains ambiguous.

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?

The definition implies usage through the "semantic vector or keyword" phrasing but never says when to pick this tool over pdf_search or workspace_search. It also never explains how an agent selects between the two modes, since no mode parameter exists.

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