Skip to main content
Glama

ADS Beast

get_lead

Read-only

Return a single lead by its ADS Beast id with every field the record holds, including email, phone, qualification answers, attribution and its current pipeline stage.

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": {
      "lead_id": "<lead_id>"
    },
    "name": "get_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesADS Beast id of the lead, as returned by get_new_leads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful response context by saying the tool returns every field the record holds and naming categories like email, phone, qualification answers, attribution, and pipeline stage. It does not mention not-found or error behavior, which is a minor gap.

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?

A single front-loaded sentence identifies the operation, key, and response breadth with no wasted wording. It is appropriately sized for a simple one-parameter read tool.

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 simple single-record read, the description identifies the lookup key and the breadth of returned fields while annotations cover the safety profile. It lacks explicit not-found/error behavior and exact return shape, but no output schema is provided and the remaining gap is minor.

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?

The single parameter is fully documented in the schema, including that it is the ADS Beast id returned by get_new_leads. The description repeats 'ADS Beast id' but adds no format, validation, or sourcing detail beyond the schema, so the high schema coverage baseline of 3 applies.

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?

States the specific verb 'Return', the resource 'single lead', and the identifying key 'ADS Beast id', so it is clearly a single-record retrieval. The word 'single' implicitly contrasts with list-style siblings, but no sibling is named.

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 by-id retrieval context is clear, but the description never explicitly states when to use this versus get_new_leads or what to do when the lead id is unknown. Usage is implied rather than guided.

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.