Skip to main content
Glama

retrieve_entities

Retrieve entities from Neotoma by type, pagination, or free-text search. Apply optional date, publication, and sorting filters for precise results.

Instructions

Use this when you need filtered entity lists (by type, pagination, and optional published/date filters) or lexical/semantic retrieval via search. Strict mode: search cannot be combined with non-default sorting or published filters. Set include_snapshots=false for lightweight responses that omit snapshot/provenance/raw_fragments. Compatibility aliases search_query and query are accepted but search is canonical.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeNoOptional entity type filter (for example: post, task, contact).
searchNoCanonical free-text query for lexical/semantic retrieval. Cannot be combined with published filters or non-default sorting.
search_queryNoCompatibility alias for `search`.
queryNoCompatibility alias for `search`.
similarity_thresholdNoSemantic distance threshold when `search` is used. Lower is stricter (typical 1.0-1.05).
limitNoMaximum number of entities to return (default 100).
offsetNoPagination offset (default 0).
sort_byNoSort field. Non-default values cannot be combined with `search`.
sort_orderNoSort direction. `desc` cannot be combined with `search`.
publishedNoFilter by snapshot.published. Cannot be combined with `search`.
published_afterNoInclusive lower bound for snapshot.published_date (ISO date/datetime). Cannot be combined with `search`.
published_beforeNoInclusive upper bound for snapshot.published_date (ISO date/datetime). Cannot be combined with `search`.
include_snapshotsNoWhen false, omit snapshot/provenance/raw_fragments payloads for lightweight responses.
include_mergedNoWhether to include merged entities (default false).
user_idNoOptional explicit user ID (normally inferred from auth context).
updated_sinceNoISO 8601 timestamp. Return only entities whose updated_at is greater than or equal to this value.
created_sinceNoISO 8601 timestamp. Return only entities whose created_at is greater than or equal to this value.
Behavior3/5

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

Discloses behavioral traits such as strict mode incompatibilities and the effect of include_snapshots. However, it omits details on error handling, authentication, or side effects. Since no annotations are provided, the description carries the full burden.

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?

Extremely concise: two sentences front-load the main purpose and key constraints. No redundant information; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 17 parameters and no output schema, the description covers primary use cases and important constraints. It could elaborate on default behavior or error handling, but schema coverage alleviates some burden.

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

Parameters4/5

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

Schema covers all parameters (100% coverage), but the description adds value by explaining interactions (strict mode) and aliases, enhancing understanding beyond individual parameter descriptions.

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 main purpose: retrieving entity lists with filtering or lexical/semantic search. It specifies verb (retrieve), resource (entities), and distinguishes from siblings by mentioning both modes and specific parameters.

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?

Provides explicit constraints (strict mode: search cannot combine with non-default sorting or published filters) and mentions compatibility aliases. Lacks explicit when-not-to-use vs alternative tools like retrieve_entity_by_identifier.

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