Skip to main content
Glama

semantic_search_entities

Read-onlyIdempotent

Search entities by natural-language query using vector embeddings, with optional entity-type filters and result limits, to find relevant countries, stocks, industries, or similar records.

Instructions

Search entities semantically using vector embeddings.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesNatural language query (e.g., "Asian countries", "technology companies")
entity_typeNoOptional filter by entity type (country, stock, industry, etc.)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description's one contribution is that matching is vector-based, implying fuzzy ranked relevance rather than exact keyword matching, which is genuinely useful context; however, it says nothing about ranking order, behavior on no matches, or result shape.

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 front-loaded sentence with no filler or redundancy. It is not padded or disorganized, though its brevity reflects under-specification rather than disciplined editing.

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?

With an output schema present and full parameter documentation, the mechanical contract for calling the tool is complete from structured data alone. The remaining gap is selection context relative to the many similarly named search siblings, which the description never addresses.

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% and all three parameters carry inline descriptions with a concrete query example and a default limit, so the schema does the heavy lifting. The description adds no meaning beyond that, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Search entities") plus a mechanism ("using vector embeddings"), but it largely restates the tool name and does nothing to separate this tool from close siblings such as semantic_search, semantic_search_unified, or ai_search. An agent knows roughly what it does but not why to pick this one.

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 when-to-use or when-not-to-use guidance and no named alternative. In a namespace crowded with semantic_search, semantic_search_unified, ai_search, and graph_search, the description offers nothing to route the agent between them.

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