Dayze — Life Context

Search Voice Transcripts

search_voice_transcripts

Read-only

Find words in the user's voice transcripts: query, person_name, limit up to 30. Returns snippets, not whole transcripts. Needs pii:read. ($0.05; API key required)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_voice_transcripts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum rows to return, e.g. 20.
`query`	Yes	Words to find in transcripts, e.g. launch plan.
`person_name`	No	Only transcripts with this contact, e.g. Alex Chen.

Output Schema

Name	Required	Description	Default
`hits`	No
`count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum rows to return, e.g. 20."
```
- addedInput schema / properties / person_name / description
```
Added value: +"Only transcripts with this contact, e.g. Alex Chen."
```
- addedInput schema / properties / query / description
```
Added value: +"Words to find in transcripts, e.g. launch plan."
```
AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real operational context: a pii:read scope requirement, a per-call cost of $0.05, an API key requirement, and the snippet-only return shape. Ordering and pagination behavior are not mentioned, but the added disclosure is substantial for a read tool.

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?

A single front-loaded sentence with the resource first, then parameters, then return shape, then auth/cost. The parenthetical cost and API-key notes are slightly crammed but each carries distinct information.

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?

With an output schema present and full schema coverage, the description needn't explain return values, and it correctly focuses on auth scope, cost, and result granularity. Only minor gaps remain, such as result ordering or whether the search spans all recordings.

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 all three parameters are already documented with examples in the schema. The description only restates the parameter names and the limit cap of 30, adding no syntax or semantic detail beyond the structured fields.

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?

States a specific verb and resource ('Find words in the user's voice transcripts') and clarifies the result granularity ('Returns snippets, not whole transcripts'), which implicitly separates it from the recording-fetch siblings. It stops short of naming an alternative tool outright.

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

Usage Guidelines3/5

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

The snippet-vs-full-transcript note gives useful context for choosing this over a recording/transcript retrieval tool, but there is no explicit when-to-use or when-not guidance and no named alternative. Usage is implied rather than directed.

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

All Dayze — Life Context tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.