Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Detect unconverted quotes

local-lead-operations_unconverted-quote-detect

Find quotes with no recorded outcome and age them from the sent timestamp. A missing outcome is not treated as a final loss. Price $0.04 USDC. POST /api/v1/local-lead-operations/unconverted-quote-detect. 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_unconverted-quote-detect"
  }
}

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, the description carries the full behavioral burden. It usefully discloses the price ($0.04 USDC), POST endpoint, 402 behavior on unpaid calls, and that missing outcomes are not treated as loss, but it omits side effects, data handling, and return behavior for a POST tool with 14 inputs.

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?

Five short sentences are front-loaded with the purpose, then payment and endpoint details. Every sentence adds either scope, semantics, pricing, or invocation behavior, with no filler.

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 tool with 14 parameters, nested objects, no annotations, and no output schema, the description is not complete enough. It covers purpose and payment but provides no input assembly guidance or output expectations.

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 coverage is 0% across 14 parameters, and the description mentions none of them. It does not explain whether to use csv, json, file, or text inputs, nor the roles of asOf, minSample, quoteLimitDays, or the leads/quotes/calls arrays.

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 ('Find quotes with no recorded outcome') and defines the aging basis ('from the sent timestamp'). It is distinguishable from sibling analyses by its focus on unconverted quotes, though it does not explicitly name alternatives.

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?

No when-to-use or when-not-to-use guidance is provided; the closest is the semantic note that a missing outcome is not a final loss. It does not direct the agent to quote-followup-priority or any other sibling.

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