Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Prioritize quote follow-ups

local-lead-operations_quote-followup-priority

Rank leads with transparent rules for missed calls, response delays, and quotes without outcomes. Priority is not a prediction that a customer will convert. Price $0.05 USDC. POST /api/v1/local-lead-operations/quote-followup-priority. 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_quote-followup-priority"
  }
}

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 does carry real weight and delivers important operational facts: the ranking uses transparent deterministic rules, the call costs $0.05 USDC, and unpaid calls return 402 and do not execute. However it says nothing about what a successful response contains, whether a minimum data set is required, or how the alternate input formats behave.

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 purpose and its non-prediction caveat are front-loaded, followed by cost, endpoint, and payment-failure behavior, with no filler sentences. The raw endpoint path is somewhat mechanical but still informative for an agent reasoning about the call.

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 high-complexity tool: 14 parameters, nested objects, up to five interchangeable input encodings, no annotations, and no output schema. The description covers purpose, price, and 402 behavior, but leaves the agent without guidance on which input form to supply, what the time-window parameters mean, or what the ranked output looks like.

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, including non-obvious ones like asOf, quoteLimitDays, responseLimitHours, minSample, and the five mutually substitutable input payload forms (csv, json, text, file, and structured arrays). The description explains none of these; the only implicit mapping is that missed calls and response delays correspond to the calls and responses collections.

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 opens with a specific verb and resource ("Rank leads") and names the three signals that drive the ranking: missed calls, response delays, and quotes without outcomes. That combination distinguishes it partially from narrower siblings like missed-call-analyze or response-delay-detect, though it never explicitly contrasts itself with them.

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 statement of when to use this tool instead of the seven overlapping siblings that cover the same underlying signals individually. The only framing is the purpose sentence plus a clarification that priority is not a conversion prediction, which describes output semantics rather than selection 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