Skip to main content
Glama

67Leads

Coverage by state or city

coverage
Read-onlyIdempotent

Lead counts per state (or per city when a state is given), optionally for one niche, so you can avoid empty searches. Free.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoNiche id from list_niches.
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds two pieces of real context beyond them: the call is 'Free' (no quota cost) and supplying a state changes the output granularity to city level. It says nothing about response shape, size, or rate behavior.

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?

A single front-loaded sentence states the output, the granularity rule, and the optional filter, followed by a two-word cost note. Nothing is padded or repeated.

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 two-optional-parameter read tool with no output schema, the description covers what is returned, at what granularity, and at what cost. The only gap is that it does not describe the shape of the returned counts, which an agent may need to plan a follow-up search.

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 coverage is only 50%, with 'state' undocumented, so the description must compensate and largely does: it explains that passing a state switches the breakdown from state-level to city-level, and that niche scoping is optional. It does not restate the niche id format, which the schema already handles.

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 the exact resource and metric (lead counts), the grouping unit (per state, or per city when a state is supplied), and the optional niche filter. An agent can tell this is an aggregate-count tool rather than a lead-listing tool, though it never names a sibling such as count_leads to sharpen the distinction.

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?

The phrase 'so you can avoid empty searches' implies the intended workflow (check coverage before running a search) and 'optionally' signals both params are optional. There is no explicit when-not guidance and no named alternative for the case where the agent actually wants individual leads.

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