Kalima

Search everything that was said

search_all_transcripts

Read-onlyIdempotent

Searches what was said across all of the user's Kalima recordings and returns single quotes with recording title, speaker and startMs, newest recordings first, e.g. "who said we would ship in Q3", "wer hat das zugesagt", "haben wir jemals über X gesprochen". A recording counts only when it contains every word of the query (or of any one of terms), and gives at most 3 quotes (search_within_recording returns all quotes in one recording). incomplete true marks a partial page: only scanned recordings are covered, and nextCursor resumes at the next recording. The query needs at least 3 characters.

Input Schema

Name	Required	Description
`mode`	No	"transcribe": transcription only. "one-way" and "two-way": with live translation.
`limit`	No	How many to return (max 20). Ask for the few you need.
`query`	No	What to search for, at least 3 characters. Optional when terms is given.
`terms`	No	Up to 10 alternatives, each at least 3 characters; a match on any one counts, e.g. ["Lia", "Lea", "Ivanti"]. Finds several names or spellings in one call. With query as well, query is one more alternative.
`cursor`	No	nextCursor from the previous call, to get the next page.
`detail`	No	"text": one text block. "speaker": text with a [speaker] label where the speaker changes. "full": segments with index, speaker and startMs.
`status`	No	Recording state: "recording" or "paused" while it runs, "stopped" or "completed" once finished.
`teamId`	No	Only recordings of this team (id from list_teams).
`projectId`	No	Only recordings in this project (exactly this one; its sub-projects are not included).
`workspaceId`	No	Personal workspace id from list_workspaces.
`nameContains`	No	Part of the recording title (case- and accent-insensitive).
`startedAfter`	No	Only recordings started at or after this ISO 8601 time (UTC if no offset).
`maxDurationMs`	No	Maximum duration in milliseconds.
`minDurationMs`	No	Minimum duration in milliseconds.
`startedBefore`	No	Only recordings started at or before this ISO 8601 time (UTC if no offset).
`organizationId`	No	Only recordings of this organization (id from list_organizations).
`unassignedProject`	No	Only recordings without a project assignment.
`unassignedWorkspace`	No	Only recordings without a workspace assignment.

Output Schema

Name	Required	Description	Default
`notice`	No
`matches`	Yes
`incomplete`	No
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only annotations it discloses the return shape (quote + recording title, speaker, startMs), ordering (newest first), match semantics (all words of query, or any one term), the 3-quotes-per-recording cap, and pagination behavior via incomplete/nextCursor. These are non-obvious traits an agent could not infer from annotations alone.

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?

Front-loaded with purpose and return shape, then matching rules and pagination, with no filler sentences. Some parenthetical density and multilingual examples add length, though they do demonstrate legitimate multilingual query support.

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 18 optional parameters, an output schema, and annotations covering safety, the description supplies the essential search semantics, ordering, cap, and pagination that structured fields cannot. It does not clarify how limit interacts with the per-recording 3-quote cap, a minor remaining gap.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning about query semantics — conjunction of words within a query versus disjunction across terms — plus the 3-character minimum. Filter parameters are left entirely to the schema, which is acceptable given full coverage.

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?

Specific verb and resource (search quotes across all recordings) with the exact result shape and ordering stated up front. It explicitly differentiates itself from the sibling search_within_recording, so an agent can pick between them without opening either schema.

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?

Names the alternative (search_within_recording returns all quotes in one recording) and provides example queries that imply typical usage. It does not explicitly route metadata-only lookups to search_recordings or state when not to use this broad scan, so it falls short of a full when/when-not guide.

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

All Kalima 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.

Resources

Need Help?