Skip to main content
Glama

Lead capture figures

lead_insights
Read-onlyIdempotent

Totals and breakdowns over captured leads — how many, of what type, and how they are landing in the CRM — optionally within a date range. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lead_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNoISO date, inclusive. Omit for all time.
startDateNoISO date, inclusive. Omit for all time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read only' is largely redundant. The description adds useful framing about what the figures cover (counts, type mix, CRM landing), but says nothing about aggregation granularity, grouping options, or response shape.

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 that describes scope first and the optional date filter second. No filler, though the trailing 'Read only' duplicates the annotations.

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

Completeness3/5

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

For a simple two-optional-parameter read tool this is close to adequate, but with no output schema the description should hint at the shape of the breakdowns it returns; 'how they are landing in the CRM' stays vague.

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 coverage is 100% and both parameters already document ISO format, inclusivity and the omit-for-all-time behavior. The description only restates that a date range is optional, adding no meaning beyond the schema.

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 resource and operation: totals and breakdowns over captured leads, with the aggregation dimensions sketched (count, type, CRM landing). This clearly separates it from list/detail siblings like lead_list or lead_detail, though it never names an alternative.

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?

Implies the use case (analytics/aggregate reporting over leads, optionally scoped to a date range) but gives no explicit when-to-use versus lead_list or lead_export, and no exclusions or prerequisites.

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.