Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Analyze missed-call leads

local-lead-operations_missed-call-analyze

Identify missed calls and whether a later response was recorded for the same lead. Delays use supplied timestamps only. Price $0.04 USDC. POST /api/v1/local-lead-operations/missed-call-analyze. Unpaid calls return 402 and do not run.

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": "local-lead-operations_missed-call-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
callsNo
leadsNo
quotesNo
sourcesNo
enquiriesNo
minSampleNo
responsesNo
quoteLimitDaysNo
responseLimitHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses pricing ($0.04 USDC), that unpaid calls return 402 without running, and that delays use supplied timestamps only, but it omits permissions, input expectations, processing behavior, and result shape for a 14-parameter analysis tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the purpose before operational details. The payment and endpoint sentences are useful, though the presentation is a bit choppy and could better group operational metadata.

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

Completeness2/5

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

For a complex paid endpoint with 14 parameters, nested objects, and no output schema or annotations, the description is incomplete. It covers cost and payment gating but leaves parameter usage, data format expectations, and return behavior largely undocumented.

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

Parameters1/5

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

Schema description coverage is 0% across 14 parameters, and the description explains almost none of them. The single timestamp constraint does not clarify what csv, json, text, file, calls, leads, responses, quotes, sources, enquiries, minSample, responseLimitHours, or quoteLimitDays mean or how they should be supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: identify missed calls and whether a later response was recorded for the same lead. It is clear what the tool does, but it does not explicitly distinguish itself from closely related siblings such as response-delay-detect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no comparison to sibling tools. An agent can infer the purpose from the one-line summary, but must guess when this tool is preferable to related lead-operations analyses.

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