Skip to main content
Glama

linepref: check before an AI agent calls a business

Report how a call went

report_call_outcome

Call this AFTER a phone call to a business ends. Sends only the number and a fixed outcome code (never a transcript, recording or names). Reporting outcomes is what unlocks pooled call data on later checks.

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>",
      "code": "<code>"
    },
    "name": "report_call_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
numberYes
countryNo
menu_pathNoKeys pressed to reach a person, e.g. "2,1". Digits, * # w and commas only.
local_hourNoHour of day at the business's location
ai_answeredNoTrue if an AI or automated receptionist answered
hold_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate this is a write operation that is not destructive. The description adds valuable privacy context beyond annotations: it sends only the number and a fixed outcome code, never transcripts, recordings, or names, and it explains that reporting unlocks pooled data on later checks.

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 short, front-loaded sentences. The timing instruction comes first, followed by privacy scope and a reason to report, with no wasted wording.

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?

Covers the essential timing and privacy behavior for a reporting tool, but with seven parameters and only 43% schema description coverage, it leaves the optional metadata parameters unexplained. No output schema exists, so return values do not need coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low at 43%, yet the description only explains the two required fields (number and code). It says 'sends only the number and a fixed outcome code' while the schema accepts optional fields such as country, hold_seconds, ai_answered, menu_path, and local_hour, and it provides no meaning for those optional fields.

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 action (report a call outcome), the resource (a phone call to a business), and the required timing (AFTER the call ends). It also makes the data boundary explicit with 'only the number and a fixed outcome code', which helps distinguish it from check/record tools.

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 clear timing guidance: 'Call this AFTER a phone call to a business ends.' It does not explicitly name alternatives or when not to use it, so it falls short of fully prescriptive 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