Agent Broker

capture_lead

Structured intake of a prospect into an SMB's funnel with validation and deduplication on (smb_id, phone or email). Stored in AgentBroker's own lead funnel, NOT the business's CRM; the business is not notified. [$0.05/per_call, not charged while no payment rail is on] [async→get_outcome] [beta]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "smb_id": "<smb_id>",
      "prospect": "<prospect>"
    },
    "name": "capture_lead"
  }
}

Input Schema

Name	Required	Description
`smb_id`	Yes
`source`	No	Where the consumer-initiated request originated (e.g., 'consumer_request',…
`prospect`	Yes
`idempotency_key`	No	Retry key: a 24h replay returns the original receipt, not re-run or charged.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged."New value: +"Retry key: a 24h replay returns the original receipt, not re-run or charged."

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / source / description

Previous value: -"Where the consumer-initiated request originated (e.g., 'consumer_request', 'inbound_quote_form', 'agent_referral_from_find_business')."New value: +"Where the consumer-initiated request originated (e.g., 'consumer_request',…"

Changed1 schema field changedAug 25, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.",
+  "maxLength": 128,
+  "type": "string"
+}

First observedAug 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, openWorld=false, idempotent=false, destructive=false). The description adds material traits beyond that: dedup semantics on (smb_id, phone or email), the storage destination and the fact that the business is NOT notified, per-call cost with the 'not charged while no payment rail' caveat, async result retrieval via get_outcome, and beta status. No contradiction with the annotations.

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?

Front-loaded with the core purpose, followed by tight bracketed metadata (cost, async routing, beta). Every clause carries information; the bracketed tags are slightly cryptic but dense rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description covers the essentials: what it does, where data lands, who is notified, cost, and that the result is retrieved asynchronously via get_outcome. The consent_record_id requirement for downstream send_message is handled in the schema. Minor gaps remain around error/validation failure behavior, but nothing critical to calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, so the description must carry weight, and it does: the dedup key '(smb_id, phone or email)' gives real meaning to smb_id and the prospect's contact fields that the schema does not. It does not elaborate on source or idempotency_key (the latter is documented in the schema), so it adds value without fully closing the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Structured intake of a prospect into an SMB's funnel') plus the dedup key and validation behavior, and explicitly disambiguates the destination ('AgentBroker's own lead funnel, NOT the business's CRM'). An agent can distinguish this from siblings like handle_inbound or send_message without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes the operating context clearly: it's AgentBroker's funnel, not the business's CRM, and the business is not notified. The '[async→get_outcome]' tag routes the agent to the follow-up tool, and the pricing note sets expectations. It stops short of naming explicit when-not-to-use conditions against siblings (e.g., when to prefer handle_inbound), so it's clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Broker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.