Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

List calls and meetings

list_calls
Read-only

Retrieve recent phone calls and meetings, newest first, with filters for channel, contact, or task to find specific interactions; each entry shows status, outcome, and cost.

Instructions

List recent phone calls and meetings, newest first, with each call's id, status, brief, outcome, and cost (on a hosted service, its charge). Filter by channel (phone or meeting), by contact (calls to or from one E.164 number), or by task id. limit defaults to 20 (at most 100); there is no paging, so narrow with the filters. Use get_call or wait_for_call for one call's full result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoTask id from a brief
limitNo
channelNo
contactNoE.164 number, such as +14155550142

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces the read-only profile while adding behavior the annotations cannot convey: newest-first ordering, a hard default of 20 with a ceiling of 100, and the absence of paging. It also clarifies the billing model ('on a hosted service, its charge'). It stops short of describing response envelope or filtering semantics for combined filters, so not a full 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 ordered as purpose/return fields, filtering semantics, then sibling routing — nothing superfluous, and the most decision-relevant information is front-loaded.

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

Completeness5/5

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

With no output schema present, the description explicitly enumerates returned fields and pagination behavior, and it covers the one significant limit constraint. Nothing an agent needs to call this tool correctly is missing.

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 only 50%, and the description compensates: 'limit defaults to 20 (at most 100)' supplies the default that the schema omits, 'contact' is clarified as an E.164 number for calls to or from it, and 'task' is tied to a brief. The channel parameter's meaning is only implied via the phrase 'phone or meeting', which matches the enum but adds little.

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?

A specific verb plus resource ('List recent phone calls and meetings') with scope (newest first) and the exact per-item fields returned (id, status, brief, outcome, cost). It explicitly contrasts with get_call and wait_for_call, so an agent can distinguish it from siblings 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 Guidelines5/5

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

States the three filtering axes (channel, contact, task id) and names the alternatives for the single-item case: 'Use get_call or wait_for_call for one call's full result.' It also gives operational guidance — no paging, so narrow with filters — which tells the agent how to use it correctly rather than just what it does.

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