Skip to main content
Glama

semantic_search_unified

Idempotent

Search entities and concepts with one natural-language query, applying optional scope and entity-type filters to return ranked results.

Instructions

Unified semantic search across both entities and concepts.

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_unified"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesNatural language query
scopeNoOptional named retrieval scope constraining concept results
entity_typeNoOptional filter by entity type (applies to entities only)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare idempotence, non-destructiveness and a closed-world scope, so the description need only add retrieval behavior — yet it says nothing about how entity and concept results are merged, ranked, or how 'unified' output is shaped. Notably, readOnlyHint=false on a search tool is counterintuitive and the description does nothing to explain or clarify it.

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 short sentence, front-loaded with the key distinguishing term 'Unified'. It is efficient, though its brevity is as much under-specification as economy.

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?

The tool takes four parameters, operates across two data domains, and returns a result set, but the description never addresses how the two domains are combined or what a caller should expect. Relying on the output schema for return values is fair, but the merge/ranking semantics are 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 description coverage is 100%, so every parameter including 'scope' and 'entity_type' is documented inline. The description adds no meaning beyond the schema, which is the expected baseline for full coverage.

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 and resource (semantic search) plus scope (entities and concepts), and the word 'unified' signals this is the combined variant rather than a single-domain search. It stops short of naming the sibling tools it consolidates, so differentiation relies on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to prefer this over semantic_search, semantic_search_entities, ai_search or graph_search, and no mention of prerequisites or exclusions. The agent must guess whether 'unified' is a superset or a fallback.

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