Skip to main content
Glama

Estimate your audience

estimate_audience
Read-only

Estimates how many decision-makers fit a business's offer.

Returns the roles, places, industries and company sizes searched; the total count; five real example people (names blurred, companies unnamed) with a fit score; the buying signals Deberli tracks for that market; and a link to sign up for Deberli. Use it when the user asks who to sell to, how big their market is, or where to find customers or leads. Read-only. Takes 30-90 seconds.

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

Input Schema

NameRequiredDescriptionDefault
briefNoOne or two sentences: what the business sells and to whom. Give this or website.
marketNoCountry or region the business sells in, e.g. United Kingdom. Without it the count covers every country.
websiteNoThe business's website, e.g. acme.com. Give this or brief.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description repeats "Read-only" rather than extending it. It does add genuine context beyond the annotations, though: the 30-90 second latency and the fact that the result includes five blurred-name example people with a fit score and tracked buying signals.

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?

The description is front-loaded with purpose and then mirrors the call's behavior, with each sentence carrying a distinct fact. It is somewhat long because it enumerates return fields, which the existing output schema already covers, so that portion is partially redundant.

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 zero-required-parameter, open-world estimation call with an output schema, the description covers purpose, trigger conditions, latency, and what the caller receives. The main gap is that it does not say what happens when neither brief nor website is supplied.

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?

All three parameters are fully documented in the schema, including the brief-or-website requirement and the market default to every country. The description adds no meaning about parameters beyond that, so the baseline of 3 applies.

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?

Opens with a specific verb and resource: "Estimates how many decision-makers fit a business's offer." That is far more informative than the title "Estimate your audience" and tells an agent exactly what the call produces.

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?

Explicitly names the triggering user intents: "who to sell to, how big their market is, or where to find customers or leads." There are no sibling tools, so no alternative routing is needed, but it also omits any when-not-to-use case (for example, when a brief or website is required versus optional).

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