Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Analyze lead source performance

local-lead-operations_source-performance-analyze

Calculate conversion rates from supplied source lead and converted counts. Ranking uses only sources that meet the disclosed sample minimum. Price $0.05 USDC. POST /api/v1/local-lead-operations/source-performance-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_source-performance-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.9/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the full burden, and it does disclose meaningful traits: a $0.05 USDC price, HTTP 402 on unpaid calls with no execution, and that ranking filters sources below the sample minimum. It does not state whether the operation is read-only, nor describe the response shape, defaults for minSample, or how input modes interact.

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?

Four short sentences, front-loaded with the core computation, then ranking behavior, then cost and transport details. The literal endpoint path is arguably padding, but nothing else is wasted.

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 14-parameter tool with nested objects, no annotations, and no output schema, the description is far too thin. It explains what is computed and the payment gate, but leaves an agent unable to choose among the five input representations or understand most parameters and the returned structure.

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 description coverage is 0% across 14 parameters, so the description must compensate and largely does not. It only hints at sources.leads, sources.converted and minSample; the csv/json/text/file alternative input modes, asOf, quoteLimitDays, responseLimitHours, and the calls/leads/quotes/enquiries/responses arrays are left entirely unexplained.

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 names a specific verb+resource: 'Calculate conversion rates from supplied source lead and converted counts'. It is clear what the tool computes, though it does not explicitly contrast itself with sibling analytics tools such as conversion-opportunity-report.

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 when-to-use guidance or routing among the seven sibling analytics tools, and no statement of prerequisites beyond payment. The ranking/sample-minimum sentence is a computation rule rather than usage 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