Skip to main content
Glama

Leadsignal

leadsignal
Read-only

AI lead generation for contractors and local service businesses. Accepts a trade type and city. Returns qualified local leads with available contact information. Required arguments: trade, city.

Input Schema

NameRequiredDescriptionDefault
_refNoOptional handover referral ID from your install link.
cityYesCity and optional state. Example: 'Chicago', 'Denver CO', 'Austin Texas'
tradeYesThe trade or service type. Example: 'plumber', 'HVAC', 'electrician', 'roofer', 'general contractor'
_zambo_keyNoOptional opaque Zambo access capability. Never place it in a URL or public log.
_session_idNoOptional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
_caller_labelNoOptional caller label recorded as a caller-reported claim in the receipt.zambo-starter
_caller_handleNoOpaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
_continuity_ai_labelNoOptional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

NameRequiredDescriptionDefault
okYes
idsYes
nextYes
tierNo
urlsYes
errorNo
graphNo
activeNo
resultYesThe tool's observed JSON value or plain-text result.
intentsNo
next_upNo
paymentNo
day_passNo
today_urlNo
expires_atNo
human_lineYes
next_stepsNo
daily_recapNo
renew_nudgeNo
unlock_linkNo
seconds_leftNo
resume_statusNo
resumed_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / _caller_handle
      Added value: +{
      +  "description": "Opaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / _caller_label / default
      Added value: +"zambo-starter"
  2. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-25"New value: +"draft-zambo-aer1-26"
  3. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-24"New value: +"draft-zambo-aer1-25"
  4. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-23"New value: +"draft-zambo-aer1-24"
  5. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-22"New value: +"draft-zambo-aer1-23"
  6. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-21"New value: +"draft-zambo-aer1-22"
  7. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-20"New value: +"draft-zambo-aer1-21"
  8. Changed1 schema field changed
    • addedOutput schema / properties / next_steps
      Added value: +{
      +  "items": {},
      +  "minItems": 1,
      +  "type": "array"
      +}
  9. Changed12 schema fields changed
    • addedInput schema / properties / _ref
      Added value: +{
      +  "description": "Optional handover referral ID from your install link.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": true,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "next_call"
      +      ]
      +    },
      +    {
      +      "required": [
      +        "next_url"
      +      ]
      +    }
      +  ],
      +  "properties": {
      +    "code": {
      +      "type": "string"
      +    },
      +    "next_call": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "args": {
      +          "type": "object"
      +        },
      +        "tool": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "tool",
      +        "args"
      +      ],
      +      "type": "object"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "next_url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "next_step"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph
      Added value: +{
      +  "properties": {
      +    "aer": {
      +      "const": "draft-zambo-aer1-20"
      +    },
      +    "schema": {
      +      "const": "zambo.graph/1"
      +    }
      +  },
      +  "required": [
      +    "schema",
      +    "aer",
      +    "nodes",
      +    "edges",
      +    "retries",
      +    "sources",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / human_line / maxLength
      Added value: +200
    • addedOutput schema / properties / human_line / pattern
      Added value: +"^[^\\r\\n]*$"
    • addedOutput schema / properties / ids
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / ok
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / renew_nudge
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / urls
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "result",
      +  "ok",
      +  "human_line",
      +  "next",
      +  "ids",
      +  "urls"
      +]
  10. Changed14 schema fields changed
    • addedOutput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / daily_recap
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / day_pass
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / human_line
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / intents
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next_up
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / resume_status
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / resumed_result
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / seconds_left
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / tier
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / today_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlock_link
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  11. Changed3 schema fields changed
    • changedInput schema / properties / _caller_label / description
      Previous value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt."
    • changedInput schema / properties / _session_id / description
      Previous value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together."
    • addedInput schema / properties / _zambo_key
      Added value: +{
      +  "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.",
      +  "maxLength": 160,
      +  "type": "string"
      +}
  12. Changed7 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +false
    • removedOutput schema / properties / city
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / count
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / leads
      Removed value: -{
      -  "items": {
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / result
      Added value: +{
      +  "description": "The tool's observed JSON value or plain-text result."
      +}
    • removedOutput schema / properties / trade
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  13. Changed2 schema fields changed
    • addedInput schema / properties / _caller_label
      Added value: +{
      +  "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
    • addedInput schema / properties / _session_id
      Added value: +{
      +  "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
  14. Changed1 schema field changed
    • addedInput schema / properties / _continuity_ai_label
      Added value: +{
      +  "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.",
      +  "maxLength": 48,
      +  "type": "string"
      +}
  15. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "city": "Austin",
      +    "trade": "electrician"
      +  }
      +]
  16. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "city": {
      +      "type": "string"
      +    },
      +    "count": {
      +      "type": "number"
      +    },
      +    "leads": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "trade": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  17. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds that it returns qualified local leads with available contact information, but it omits operational context around the optional _zambo_key, _session_id, and continuity parameters, and gives no detail on rate limits or what 'qualified' means. This is useful but not rich behavioral disclosure.

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 short and front-loads the core purpose before inputs and outputs. It is slightly redundant in saying both 'Accepts a trade type and city' and 'Required arguments: trade, city,' which prevents a perfect score, but otherwise every sentence is useful.

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

Completeness3/5

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

An output schema exists, so return values need not be explained in detail. However, for a tool with eight parameters and several optional session/continuity arguments, the description does not address when to use the tool or how the optional operational parameters fit into a workflow. It is adequate for basic invocation but incomplete as agent guidance.

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 description coverage is 100%, so all eight parameters, including the optional operational ones, are fully documented in the schema. The description only restates the required trade and city arguments, adding no meaning beyond what the schema already provides. Baseline 3 is appropriate given complete schema coverage.

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 resource: generating qualified local leads for contractors and local service businesses, parameterized by trade and city. It clearly communicates what the tool does, but it does not differentiate itself from any sibling tools such as handover or zambo_home.

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?

The description says it accepts trade and city and lists them as required, which implies usage, but it gives no explicit guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. It effectively leaves routing decisions to the agent.

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