Skip to main content
Glama

BRAINIAC Local Business Lead Operations

Classify customer enquiries

local-lead-operations_customer-enquiry-classify

Classify enquiry text with transparent token rules such as emergency, quote, booking, or complaint. Classification is not a conversion prediction. Price $0.04 USDC. POST /api/v1/local-lead-operations/customer-enquiry-classify. 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_customer-enquiry-classify"
  }
}

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

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

No annotations are supplied, so the description must carry behavioral context; it does disclose paid pricing, the POST endpoint, and a 402 failure mode for unpaid calls. It does not state whether classification is read-only or idempotent, how the token rules behave, or what side effects or return values to expect.

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 description is compact and front-loads the core action and categories before billing and endpoint details. It is mostly efficient, though the endpoint string and payment/failure sentences are operational rather than selection-critical.

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, zero schema descriptions, no annotations, and no output schema, the description provides only a high-level purpose plus billing information. It leaves parameter usage, accepted input combinations, and result behavior largely unexplained.

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?

The schema has 14 parameters with 0% description coverage, including many arrays (enquiries, leads, calls, quotes, responses) and alternate payload forms (text, csv, json, file). The description only hints at 'enquiry text' and adds no meaning for the rest, leaving most parameters opaque.

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 uses a specific verb-resource pair ('Classify enquiry text') and lists rule-based categories, so the action is clear. It also states it is not conversion prediction, which separates it from forecasting siblings, but it does not name an alternative tool explicitly.

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 when-to-use guidance or named alternative among the sibling operations. The 'not a conversion prediction' line is a caveat or exclusion, but it is not a routing rule for choosing this classifier.

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