Skip to main content
Glama

retrieve_entity_by_identifier

Retrieve any entity by identifier (name, email, tax_id) across types, with fallback to semantic search when exact match fails.

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?

The description adds the fallback to semantic search, which is beyond what the schema or missing annotations provide. However, it omits details about multiple matches, response structure, or potential side effects, so transparency is adequate but not comprehensive.

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 sentences with no fluff: the first captures the core action, the second provides a critical behavioral detail. All words serve a purpose.

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?

The description is sufficient for basic usage but lacks details about return format or behavior for edge cases (e.g., no match, multiple matches). Given the absence of an output schema, some additional context would improve completeness.

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 the baseline is 3. The description does not add significant new meaning per parameter beyond what is already in the schema (e.g., identifier normalization is mentioned but not new).

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?

The description clearly states the verb 'retrieve' and resource 'entity by identifier', listing example identifiers. It distinguishes from siblings like 'retrieve_entities' (plural retrieval) and includes a fallback mechanism, making the tool's purpose specific and unambiguous.

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

Usage Guidelines4/5

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

The description indicates when to use the tool (having an identifier) and mentions optional entity_type filtering, but does not explicitly exclude cases when other tools like 'retrieve_entity_snapshot' or 'retrieve_entities' would be more appropriate.

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