Skip to main content
Glama

linepref: check before an AI agent calls a business

Record an opt-out request from the called party

record_opt_out

Call this when the called party asks to stop receiving calls (by voice or key press). scope "caller" stops calls from this caller; scope "all" records that they asked to stop AI assistant calls from all participating callers. Honour it within ten business days.

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": {
      "number": "<number>",
      "scope": "<scope>"
    },
    "name": "record_opt_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes
numberYes
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds genuinely useful context beyond that: the caller vs all participating callers distinction implied by scope, and a ten-business-day compliance obligation. It does not say whether the opt-out takes effect immediately for future calls, whether it can be reversed or re-recorded, or what the tool returns on success.

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?

Two front-loaded sentences: the trigger condition comes first, then the scope semantics and compliance window. No filler, and the compliance deadline is substantive rather than padding.

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

Completeness3/5

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

For a write operation with no output schema and no schema descriptions on any parameter, the definition leaves meaningful gaps: what 'number' refers to, why 'country' exists, and what effect/confirmation the agent should expect. The compliance and scope content is good, but the definition is not fully self-sufficient for correct invocation.

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 0%, so the description must carry the parameter meaning, and it only partly does: it fully explains the 'scope' enum ('caller' stops calls from this caller; 'all' covers all participating callers). The 'number' parameter is never tied to the called party's number, and the optional 'country' parameter is not mentioned at all, leaving two of three parameters to inference.

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+resource (records an opt-out request) and the exact trigger event: the called party asking to stop receiving calls, by voice or key press. This is clearly distinguishable from check_before_call, check_many and report_call_outcome, which are read/check or outcome-reporting operations.

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 when-to-use condition ('call this when the called party asks to stop receiving calls') and explains the two scope modes. It stops short of naming an alternative tool or stating when not to call it (e.g. duplicate opt-outs, or handling a request that is really a complaint), so it is strong but not complete routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources