Skip to main content
Glama

Get a Lead Finder report

get_lead_finder_report
Read-onlyIdempotent

One saved Lead Finder / Competition Analysis audit report: score, score breakdown, report data and competitor summary. Use list_analysis_reports for ids. Reads the saved report only; no credits.

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": {
      "report_id": "<report_id>"
    },
    "name": "get_lead_finder_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds context beyond that which structured fields do not carry: 'Reads the saved report only; no credits' tells the agent the call has no credit cost and no side effects on fresh data. It does not cover error behavior for an unknown report_id.

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?

Two short sentences with no filler: the returned content is front-loaded, followed by the id prerequisite and the read-only/no-credit note. Every clause carries information an agent would act on.

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 single-parameter read tool with no output schema, the description carries the right burden: it sketches the returned payload and rules out credit consumption. 'report data' is the one vague element, and nothing is said about what happens when the id does not resolve.

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 0% for a single required report_id, so the description must compensate. It does so partially by stating the id source ('Use list_analysis_reports for ids') and that it refers to a saved report, while the UUID format is supplied by the schema. It adds no detail on validity or failure modes for the id.

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 names the specific resource ('One saved Lead Finder / Competition Analysis audit report') and enumerates what it contains (score, score breakdown, report data, competitor summary), so the object of retrieval is unmistakable. The verb is only implied by the phrase 'One saved ... report', and it explicitly points away from the list sibling, which keeps it just short of a fully explicit verb+resource statement.

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?

'Use list_analysis_reports for ids' gives a concrete prerequisite and routes the agent to the right alternative for discovery. There is no explicit when-not-to-use guidance (e.g. what to do if the report is missing or stale), but the calling context is otherwise clear.

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