Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Detect lead response delays

local-lead-operations_response-delay-detect

Calculate hours from enquiry received time to the first recorded response. Overdue uses the disclosed hour limit and does not claim conversion. Price $0.04 USDC. POST /api/v1/local-lead-operations/response-delay-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_response-delay-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 burden and does disclose genuinely useful behavior: a $0.04 USDC price, a POST transport, and that unpaid calls return 402 without executing. However, it leaves the core computation opaque — 'the disclosed hour limit' is never pinned to the responseLimitHours parameter, and nothing explains minSample, asOf, or how missing responses are handled.

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 with the core computation front-loaded, then commercial and failure-mode details. The raw endpoint string adds little for an agent but is brief, and no sentence is padded.

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 tool with 14 mostly nested parameters, no required fields, no output schema and no annotations, the description covers purpose and payment gating but says nothing about input shape, precedence among csv/json/text/file, or what the result contains. An agent could not construct a correct call from this alone.

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 fails to. Only the 'disclosed hour limit' phrase hints at responseLimitHours; the csv/json/text/file input modes, leads/enquiries/responses arrays, asOf, and minSample all receive no explanation.

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 opening sentence gives a specific verb and resource: calculating elapsed hours between an enquiry's received time and the first recorded response. That is concrete enough to distinguish it from analytical siblings like missed-call-analyze or unconverted-quote-detect, though it never explicitly names an alternative.

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 and no named alternative. The clause 'does not claim conversion' is a scope disclaimer about outputs rather than a routing rule, so an agent gets no help deciding between this and the other lead-operations tools.

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