Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Normalize lead records

local-lead-operations_record-normalize

Copy supplied leads, calls, quotes, responses, and enquiries into a consistent inventory. Counts come from the request only. No CRM account is accessed. Price $0.04 USDC. POST /api/v1/local-lead-operations/record-normalize. 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_record-normalize"
  }
}

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.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses the price ($0.04 USDC), the payment gate (402, call does not run), and that no CRM account is accessed, so there are no external side effects. It falls short of explaining whether the normalized inventory is persisted or merely returned, and gives no idempotency or repeat-call semantics.

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?

Five short sentences, front-loaded with the action and scope, then constraints, price, and endpoint. The endpoint path and price are functional rather than filler, though the URL adds little for an agent that already selected the tool.

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 output schema, and no annotations, the description is thin: it never explains what the returned "consistent inventory" looks like or what the limit/sample parameters do. An agent can grasp the intent but not call it confidently.

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 it only gestures at five of the arrays (leads, calls, quotes, responses, enquiries). It says nothing about sources, csv, json, text, file, asOf, minSample, quoteLimitDays, or responseLimitHours, leaving most parameters undocumented anywhere.

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 multiple concrete resources ("Copy supplied leads, calls, quotes, responses, and enquiries into a consistent inventory"), which is far more specific than a restatement of the title. It does not explicitly distinguish itself from the sibling analysis tools, but the ingest/normalize framing is clear enough to separate it from reporting tools.

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 explicit guidance on when to use this tool versus the sibling analytics tools, nor on sequencing (e.g., normalize first, then analyze). The phrases "supplied" and "Counts come from the request only" imply the caller must pass data in rather than pull from a CRM, but that is inference rather than stated 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