Skip to main content
Glama

A lead's dossier

get_lead
Read-onlyIdempotent

One person of a search: the profile card, the company, the verdict and why they fit, each criterion's status with how it was checked, and the facts found (dated, with source links) — the material for a personal message. [REST: GET /api/tasks/{id}/candidates/{cid}]

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

Input Schema

NameRequiredDescriptionDefault
cidYesThe person's id (cid) from list_leads.
task_idYesThe search id (task id), e.g. from list_searches or create_search.

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 it a safe, idempotent, closed-world read, so the description's job is to add context — and it does by disclosing the shape of the payload (verdict plus reasoning, per-criterion status with how it was verified, facts with dates and source links). That is meaningful behavior beyond the annotations, since there is no output schema to convey it. The REST path tag is a small extra transparency bonus for debugging.

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 sentence that front-loads the identity of the resource and then enumerates payload contents compactly; the appended REST endpoint is a minor non-essential tail. The em-dash enumeration is dense but every item names a distinct piece of returned data, so little is wasted.

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 no output schema, the description carries the return-value burden and discharges it by listing the dossier's components, which is exactly what an agent needs to decide whether to fetch this or a lighter sibling. The gaps — explicit selection guidance and any error behavior for an unknown cid — are modest for a read-only two-parameter tool.

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

Parameters4/5

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

Schema description coverage is 100% and both parameters carry their own explanations, including provenance ('cid from list_leads', 'task id from list_searches or create_search'). The description adds nothing about the parameters themselves, so the baseline applies rather than something higher.

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 enumerates exactly what a single lead record contains (profile card, company, verdict and rationale, per-criterion status, sourced facts), which tells an agent this is a per-person detail fetch rather than an aggregate. It never states the verb cleanly — 'One person of a search' is an elliptical noun phrase rather than 'Get one lead', and the retrieval verb is only inferable from the name and the REST GET tag. Still, the resource is unambiguous and clearly distinct from list-type siblings.

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: 'the material for a personal message' signals the downstream purpose (composing outreach to one person), which helps an agent pick this when it needs full detail on a specific lead. There is no explicit when-not, no mention of alternatives such as get_outreach_lead, and no statement of prerequisites (that cid must come from list_leads is left to the schema).

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