Skip to main content
Glama

retrieve_entity_by_identifier

Retrieve entities by identifier (name, email, etc.) with optional type filtering, using keyword search or semantic fallback.

Instructions

Retrieve entity by identifier (name, email, etc.) across entity types or specific type. Falls back to semantic search when keyword match returns no results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesIdentifier to search for (name, email, tax_id, etc.) - will be normalized
entity_typeNoOptional: Limit search to specific entity type (e.g., 'company', 'person')
byNoRestrict snapshot-field matching to a single field (e.g. 'email', 'domain', 'company'). When omitted, checks a default identity-bearing set (name, full_name, title, email, domain, company).
limitNoMax matching entities (default 100).
include_observationsNoWhen true, include recent observations per matched entity (ordered by observed_at desc).
observations_limitNoMax observations per entity when include_observations is true (default 20, max 200).
Behavior3/5

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

Without annotations, the description carries full burden. It discloses the fallback to semantic search, but does not mention authorization, rate limits, or idempotency. Minimal but adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-loading the purpose and key behavior (fallback). No wasted words.

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?

Given no output schema, the description does not explain return format. It covers fallback behavior but lacks details on pagination or default limits (though in schema). Adequate but could improve.

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. The description adds no additional meaning beyond the schema's parameter descriptions.

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 clearly states the tool retrieves an entity by identifier (name, email, etc.) and mentions fallback to semantic search. It distinguishes itself from siblings that may list all entities or retrieve by snapshot.

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?

No explicit guidance on when to use this tool vs alternatives like retrieve_entities or retrieve_entity_snapshot. The fallback behavior is described but no when-not-to-use advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markmhendrickson/neotoma'

If you have feedback or need assistance with the MCP directory API, please join our Discord server