Skip to main content
Glama

Agent Broker

by io.github.basilalshukaili
OverviewDiscussionsAdmin

capture_lead

Structured intake of a prospect into an SMB's funnel with validation and deduplication on (smb_id, phone or email). Stores the prospect in the SMB's AgentBroker lead funnel — this is AgentBroker's own lead store, NOT a write into the business's own CRM. [$0.05/per_call] [async→get_outcome]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smb_idYes
sourceNoWhere the consumer-initiated request originated (e.g., 'consumer_request',…
prospectYes
idempotency_keyNoRetry key: a 24h replay returns the original receipt, not re-run or charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • 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',…"
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed2 schema fields changed
    • changedInput schema / properties / prospect / properties / consent_record_id / description
      Previous value: -"ID of consent record if marketing opt-in obtained"New value: +"Optional ID of a consent record proving the prospect asked to be contacted (e.g., they filled an SMB's intake form or requested a quote). Required when downstream send_message calls are anticipated."
    • changedInput schema / properties / source / description
      Previous value: -"Channel or campaign that sourced this lead"New value: +"Where the consumer-initiated request originated (e.g., 'consumer_request', 'inbound_quote_form', 'agent_referral_from_find_business')."
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds valuable context: it is a mutation that stores a prospect, performs validation and deduplication, is async, and incurs a cost. It also clarifies the storage domain (AgentBroker's store) which prevents misuse. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense sentence that front-loads the core purpose, includes critical distinctions (not CRM), and appends cost and async behavior. Every element earns its place with no redundancy.

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?

The description covers the main purpose, storage location, deduplication logic, cost, and async flow. The nested prospect object is detailed in the schema, and the idempotency behavior is described in the parameter schema. While it does not explain the return format or all edge cases, it is sufficient for an agent to call the tool correctly.

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

Parameters3/5

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

Schema coverage is 50%, so the description must compensate. It adds meaning to smb_id and prospect's phone/email by identifying them as deduplication keys, and it mentions the idempotency_key parameter implicitly through the 'async→get_outcome' note (though not explicitly). However, it does not explain other parameters like source, notes, or consent_record_id, leaving some gaps.

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?

The description clearly states the tool's function: structured intake of a prospect with validation and deduplication on (smb_id, phone or email). It also explicitly clarifies the storage location (AgentBroker's lead store, not the business's CRM), distinguishing it from potential alternatives. This is specific and unambiguous.

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

Usage Guidelines3/5

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

The description implies when to use this tool (when capturing a prospect) and notes the async flow with get_outcome, but it does not explicitly name alternative tools or state conditions for not using it. The clarification that it does not write to the business's own CRM serves as an implicit exclusion, but there is no explicit routing guidance.

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

All Agent Broker toolsInspect
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.

Resources