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

Smitline: AI Phone Calls & Meetings

Save notes from a call

save_call_note
DestructiveIdempotent

Save a short note after a call to carry quotes, terms, and dates into follow-up calls that reference this call, instead of relying on the call summary.

Instructions

After a call ends, save a short note for later calls, such as the quote, terms, and dates a business gave. Later calls start with it when their brief's carryFrom names this call, its task, or its number. Without a note, later calls use the call's summary instead.

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": {
      "callId": "<callId>",
      "text": "<text>"
    },
    "name": "save_call_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
callIdYesCall id returned by start_call, such as call-0123456789abcdef

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-readonly, destructive, idempotent, closed-world, so the safety bar is partly covered. The description adds real value beyond them: it explains propagation (which later calls will actually receive the note), the scoping key (carryFrom by call, task, or number), and the fallback behavior (summary is used when no note exists). It does not say whether saving replaces an existing note on the same call, which is the main behavioral gap for a destructive, idempotent write.

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 tight sentences: trigger, effect, and fallback. It is front-loaded with the timing condition and no sentence is redundant — even the fallback sentence tells the agent why an absent note matters.

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 two-parameter write tool with annotations and no output schema, the description covers purpose, timing, content guidance, and downstream consumption. The remaining hole is what the call returns and whether an existing note is overwritten, neither of which is recoverable elsewhere since there is no output schema.

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 covers 50%: callId is documented in-schema, but text only has a maxLength. The description compensates by characterizing what text should contain ("a short note ... such as the quote, terms, and dates a business gave"), which is exactly the guidance the schema lacks, though it does not explain behavior at the 1200-character boundary.

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?

States a specific verb and resource ("save a short note"), names the timing anchor ("after a call ends"), and describes the content the note carries (quote, terms, dates). An agent can distinguish this from end_call or get_call without opening any 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 a clear triggering condition ("after a call ends") plus the consumer condition that makes a note worthwhile: later calls whose brief's carryFrom names this call, task, or number. No explicit when-not-to-use or named alternative is given, but the selection context is unambiguous.

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