Skip to main content
Glama

Get one captured lead

lead_detail
Read-onlyIdempotent

Everything captured for one lead by its capture id, including the individual captured fields and whether it reached the CRM. Read only.

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": {
      "captureId": "<captureId>"
    },
    "name": "lead_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
captureIdYesThe lead's capture id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / captureId / description
      Previous value: -"The capture id, as returned by lead_list"New value: +"The lead's capture id"
  2. 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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the 'Read only.' clause earns no credit. What does add value is the disclosure of payload content — the individual captured fields plus whether the lead reached the CRM — which tells the agent what it will receive even though no output schema exists.

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?

A single front-loaded sentence carries the scope and return content, followed by a short safety tag. 'Read only.' duplicates the annotations and is the only wasted text; otherwise the description is tight and well-ordered.

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

Completeness5/5

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

For a one-parameter, single-record read tool with full annotation coverage and no output schema, the description supplies exactly what is needed: the identifying key, the scope (one lead), and the expected payload including CRM delivery status. Nothing essential 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.

Parameters3/5

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

Schema description coverage is 100% and the single captureId parameter is already documented in the schema; the description only restates that the lookup is by capture id. Baseline 3 applies since the schema carries the parameter burden and the description adds no format, sourcing, or id-provenance detail.

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 a clear resource and scope: 'Everything captured for one lead by its capture id', which distinguishes it from the list/insights siblings by qualifying 'one lead' and specifying the capture id as key. The verb is implicit ('Everything captured for...') rather than an explicit 'retrieve', and no sibling is named directly, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool to call when it has a single capture id and needs that lead's full detail. There is no explicit when-to-use statement, no mention of when to prefer lead_list, lead_insights, or lead_export, and no prerequisites or error conditions.

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.