Skip to main content
Glama

Search entities

search_entities
Read-onlyIdempotent

Find entities by name or description, or filter them by type and attributes.

With ``query``: returns ranked candidates, each with ``method`` (how it
was found), ``score`` (0-1), ``legacy``, ``relaciones`` (counts by
state) and ``contexto`` (up to 4 relations, current first, to tell
similarly named entities apart). Methods, most to least reliable:
exacta, alias, parcial (whole word or same words), semantica (name
similarity) and memoria (entity mentioned in the closest episodes).
semantica and memoria results appear only for multi-word queries and
are candidates, not confirmed matches. A single word with no lexical
match returns []. If nothing is found, the item may still exist in
memory without being an entity (see retrieve_memories).

Without ``query``: returns all entities matching entity_type and/or the
given attribute values, with no result limit. With no query and no
filters it returns every entity.

Args:
    query: A name, part of a name, or a short description.
    entity_type: Filter by type (only without query). 'unclassified'
        means entities whose type is not known.
    attributes: Exact attribute key-value pairs to match (only without
        query).
    limit: Maximum results for a query search (1-50).
    via_memoria: With query, set False to skip episode-based matches and
        search names only.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
attributesNo
entity_typeNo
via_memoriaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, but the description goes far beyond: it enumerates the ranking methods (exacta, alias, parcial, semantica, memoria) with reliability ordering, warns that semantica/memoria results are candidates not confirmed matches, discloses that single-word no-match returns [], and that unfiltered calls return every entity with no limit. This is rich behavioral disclosure.

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?

Front-loaded with the core purpose and the two modes, and every sentence carries distinct information. It is longer than typical but nearly all of it is load-bearing, so it earns its length rather than wasting it.

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 no output schema, the description compensates by describing the return fields (method, score, legacy, relaciones, contexto) and the empty-result behavior. For this complexity level (5 params, nested attributes object, dual modes), nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the burden, and it does: it documents all five parameters including argument semantics (what `query` accepts, that 'unclassified' is a special type, that `attributes` are exact key-value matches, the 1-50 limit range, and `via_memoria=False` skipping episode matches).

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 the specific verb+resource ('Find entities by name or description') and immediately distinguishes two distinct operating modes (with query vs without query), which separates it from siblings like list_entities and get_entity. An agent can tell exactly what this tool does.

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?

Explicitly delineates when to use each mode: query for ranked/fuzzy search, no query for full filtered listing, and it names retrieve_memories as the fallback when nothing is found. `entity_type` and `attributes` are flagged as 'only without query', preventing misuse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources