GoodLeads

Look up one lead by ID

find_lead_by_glid

Read-onlyIdempotent

One record in full, by its Lead ID (e.g. GL-CO-00042).

Use this when you already hold a Lead ID — from a file, a CRM, a receipt —
and want everything we know about that business and its owner: the
business, the primary contact, both scores, every attribute, and where
each field came from.

Args:
    glid: The Lead ID, e.g. `GL-CO-00042` — the `lead_ref` field on every
        record. Case-insensitive.

Returns:
    The full lead detail dict, including a `_meta` provenance block
    (schema_version, freshness incl. this record's last update, source,
    score_versions, access_level). Includes `history`: every event the state
    has published about this business, newest first, each with
    `published_date`, `event` (plain words) and `effective_date` when it
    differs; for a business that changed form, `prior_entity_ref` and
    `prior_entity_formation_date` name the record it came from. The
    `entity` carries `filing_kind` and `lead_class`. The history is free
    without a key; only the person is masked. Raises ValueError if the id
    is not shaped like a Lead ID or no record matches.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`glid`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With annotations already marking it read-only and idempotent, the description adds substantial behavior: case-insensitive ID matching, ValueError on malformed or unmatched IDs, free history with only the person masked, newest-first ordering, and a _meta provenance block. This goes well beyond the annotation safety profile and prepares the agent for error cases and output shape.

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?

The description is front-loaded with the one-sentence purpose and usage condition, then organized into Args and Returns sections. Although the Returns section is detailed, every clause conveys a decision-relevant behavior (ordering, masking, errors, provenance), so no sentence feels wasted.

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 single-parameter lookup tool with no parameter schema description, the description is complete: it covers ID format, input source, output contents, provenance, history, access/masking, and error behavior. An agent has everything needed to decide to call it and to interpret the result.

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

Parameters5/5

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

The sole parameter `glid` has no description in the schema (0% coverage), so the description carries the full burden. It explains the parameter means the Lead ID, gives a concrete example (`GL-CO-00042`), maps it to the `lead_ref` field on every record, and notes case-insensitivity. This fully compensates for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names the exact operation and resource: 'One record in full, by its Lead ID' with format. The description then specifies precisely what is returned (business, contact, scores, attributes, provenance), which distinguishes this from list/browse siblings like browse_leads. This is a specific verb+resource, not a restatement of the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use it: 'Use this when you already hold a Lead ID — from a file, a CRM, a receipt — and want everything we know about that business.' It gives clear context for choosing this over browsing/searching. It does not name sibling alternatives or state a when-not condition, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GoodLeads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?