Convocore

call_logs_read

Read-onlyIdempotent

Read voice call logs of the workspace (web, inbound and outbound calls). Actions: list (filter by agent, type, phone numbers, date range, search; paginated), get (one call by callLogId — transcript and latency data only with mode="full"), export (JSON or CSV of many calls; includeTranscripts=true to add transcripts). Chat conversations are in list_conversations, not here.

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": {
      "action": "<action>"
    },
    "name": "call_logs_read"
  }
}

Input Schema

Name	Required	Description
`mode`	No	compact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
`page`	No
`type`	No
`limit`	No	List page size, default 20, max 100.
`action`	Yes
`format`	No	For export. Default json.
`search`	No
`agentId`	No
`maxRows`	No	For export. Default 1000, max 5000.
`startTo`	No	ISO datetime.
`callLogId`	No	Required for get (UUID).
`sessionId`	No
`startFrom`	No	ISO datetime, e.g. "2026-10-01T00:00:00.000Z".
`agentPhone`	No
`callLogIds`	No	For export: only these call log ids.
`customerPhone`	No
`includeTranscripts`	No	For export. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior beyond them: pagination on list, that get yields transcript and latency data only with mode="full", and that export can optionally add transcripts. It doesn't mention result size shock, rate limits, or what happens with an invalid callLogId, keeping it below 5.

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?

Three dense sentences with the resource and scope front-loaded, then action semantics, then the disambiguation line. Nothing is redundant and no sentence can be dropped without losing routing 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?

For a 17-parameter, action-switched read tool with no output schema, the description covers the decision surface an agent needs: which action, which filters, and the transcript caveat. Remaining gaps (sessionId/page semantics, response shape/pagination envelope) are modest given readOnly annotations and schema-described limits.

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?

With 53% schema coverage the description must compensate, and it only partly does. It usefully ties parameters to actions (agent/type/phone/date/search filters for list, callLogIds/maxRows/format/includeTranscripts for export, callLogId for get), but several params — sessionId, page, agentId, customerPhone, agentPhone — carry no meaning in either place. Some of its content (mode, format, includeTranscripts defaults) merely restates schema 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?

Names a specific verb and resource ("Read voice call logs of the workspace") and immediately scopes it to web, inbound and outbound calls. It enumerates the three actions (list/get/export) and explicitly excludes chat conversations by pointing to list_conversations, so an agent can distinguish it from the sibling conversation tools without opening a 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?

Gives per-action routing: list for filtered browsing, get for a single callLogId, export for many calls as JSON/CSV. It also names the decisive option (mode="full" needed for transcript/latency) and the explicit exclusion ("Chat conversations are in list_conversations, not here"). It stops short of naming alternatives such as query_conversations or export_all_conversations, so a 4 rather than 5.

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

All Convocore 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?