memoket

search_recordings

Read-only

[search] Unified recording search. Runs bounded searches over transcript lines, topic segments, memory atoms, participant metadata, titles, briefs, summaries, and action items in one call. Returns typed hits plus conversation_ids, line_ids, segment_ids, memory_atom_ids, participant_ids, brief_ids, summary_ids, action_item_ids. Chat execution expands hits into readable evidence automatically; external callers can fetch returned ids where a matching fetcher is advertised.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Required. One phrase for a single concept, or a JSON array string of 2-4 distinct facets.
`end_time`	No	ISO 8601; filters by recording started_at.
`start_time`	No	ISO 8601; filters by recording started_at.
`search_types`	No	Optional lane filter. Omit to search all. Allowed: transcript, segment, memory_atom, participant, title, brief, summary, action_item.
`conversation_ids`	No	Optional: restrict to these opaque recording ids.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes
`result`	Yes	Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
`took_ms`	No

TDQS

A4.2/5.0

Behavior4/5

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

Description adds behavioral context beyond annotations: 'bounded searches' implies limits, and explains automatic expansion in chat. No contradiction with readOnlyHint=true and destructiveHint=false.

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 wasted words. Front-loaded with core purpose, then lists return types and execution notes. Highly efficient.

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?

Covers all key aspects: search types, return IDs, execution modes. Could mention pagination or limits explicitly, but overall adequate given the tool's complexity and presence of output schema.

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 parameters are well-documented. The description adds minimal extra meaning beyond what the schema provides (e.g., 'bounded searches' is not parameter-specific). Baseline 3 applies.

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 tool performs unified recording search across multiple data types (transcript, topic, memory, participant, etc.) in one call, distinguishing it from sibling tools that retrieve specific record types like get_brief or get_conversations.

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 clear context that for chat execution hits are expanded automatically, while external callers fetch IDs for advertised fetchers. Does not explicitly state when not to use, but purpose differentiation with siblings is strong.

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

All memoket tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool targets a distinct aspect: metadata, content types (brief, summary, transcript), filtered transcript, listing, and search. No two tools overlap in purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case (get_*, list_*, search_*), making their actions predictable.

Tool Count5/5

Seven tools cover the retrieval scope without being too many or too few; each serves a clear function in the conversation management domain.

Completeness3/5

The server lacks direct fetchers for several result types from search (e.g., memory_atoms, segments, action_items), creating dead ends for agents that need to retrieve those details.

Resources

Need Help?