Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Report lead conversion opportunities

local-lead-operations_conversion-opportunity-report

Combine unanswered missed calls, response delays, unconverted quotes, source rates, and enquiry classes from supplied records. No messages are sent and conversion is not claimed. Price $0.12 USDC. POST /api/v1/local-lead-operations/conversion-opportunity-report. 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_conversion-opportunity-report"
  }
}

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

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses important traits: no messages are sent, conversion is not claimed, the price is $0.12 USDC, and unpaid calls return 402 without running. It does not describe rate limits, data handling, or the exact report contents, but the key safety and payment behaviors are stated.

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?

The description is four short sentences and front-loads the tool's purpose before adding safety, pricing, endpoint, and payment-failure details. Every sentence adds useful information with no wasted wording.

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?

This is a complex tool with 14 parameters, nested objects, no output schema, and no annotations. The description covers the high-level purpose and payment behavior but leaves the input schema largely unexplained and does not describe the report's return content, making it incomplete for correct invocation.

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?

The schema has 14 parameters at 0% description coverage, so the description must compensate. It loosely identifies data domains such as calls, responses, quotes, sources, and enquiries, but it does not explain csv/json/text/file alternatives, asOf, minSample, quoteLimitDays, responseLimitHours, leads, or most nested fields.

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: it combines missed calls, response delays, unconverted quotes, source rates, and enquiry classes from supplied records into a conversion-opportunity report. The purpose is clear, but it does not explicitly name or differentiate itself from the sibling component-analysis tools.

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

Usage Guidelines3/5

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

The list of combined analyses implies this tool is for a consolidated report rather than a single analysis, but there is no explicit when-to-use guidance or comparison to the sibling tools. The agent must infer that this is the aggregate option.

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