Skip to main content
Glama

Get Lead Tool

get-lead
Read-only

Returns one authorized lead using bounded contact, source, status, and service-interest fields; notes, budget, and internal summaries are excluded. Use to get lead in the connected business. Returns lead, scope.

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_idYesLead ID returned by search-leads.

Output Schema

NameRequiredDescriptionDefault
leadYesLead data returned by the authorized safe projection.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "lead_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "lead": {
      +      "description": "Lead data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "lead",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: a field-level projection that excludes notes, budget, and internal summaries, and an "authorized" scoping qualifier that hints at permission filtering. It stops short of saying what happens when the lead is missing or unauthorized.

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

Conciseness3/5

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

The first sentence is dense, front-loaded and earns its place. The trailing "Use to get lead in the connected business. Returns lead, scope." is tautological and the "Returns lead, scope" fragment is cryptic boilerplate that adds no usable information.

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?

With an output schema present and annotations covering safety, the description needn't describe return values, and it usefully covers field visibility and authorization scope. Only the missing failure/not-found behavior and sibling routing keep it below complete.

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 lead_id is documented as "Lead ID returned by search-leads," so the baseline is 3. The description adds no syntax, format, or validation meaning beyond what the schema already provides for the single parameter.

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 specific verb and resource ("Returns one authorized lead") plus the exact field scope (contact, source, status, service-interest) and what is excluded (notes, budget, internal summaries). This clearly distinguishes it as a single-record read, but it never names or contrasts with a sibling list tool such as search-leads, which only appears buried in the schema.

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?

"Use to get lead in the connected business" is essentially a restatement of the tool name rather than when-to-use guidance. The single-record framing plus the schema note that lead_id comes from search-leads implies the retrieve-vs-search split, but the description itself gives no explicit alternatives or exclusions.

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