Skip to main content
Glama

Data Candy: US business leads

Database overview

database_overview
Read-onlyIdempotent

Overview of the Data Candy US business-lead database: how many records it holds, how many have an email, a mobile number or a website, how fresh the data is, the fields on each lead, and the current prices and payment options. Free, no account needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
linksYes
catalogYesThe catalog overview from /v1/catalog: totals, coverage per field, freshness, fields.
pricingYes
total_leadsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context not present in structured fields: the call is free and requires no account, which matters for an agent deciding whether it can invoke it early in a workflow.

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 compact sentence with a front-loaded subject ("Overview of the Data Candy US business-lead database") followed by the enumerated contents and the free/no-account note. Every clause carries information; the comma-separated list is dense but readable and wastes no words.

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?

With zero parameters, an output schema that already documents the return shape, and annotations covering safety and idempotency, the description supplies everything an agent still needs: what domain the overview covers and that access is free and unauthenticated. No material gap remains for a tool this simple.

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?

The tool takes zero parameters and the schema has additionalProperties=false, so there is no parameter semantics to explain. Baseline 4 applies; nothing in the description misleads about inputs.

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 (the Data Candy US business-lead database) and enumerates exactly what the overview reports: record counts, email/mobile/website coverage, data freshness, per-lead fields, and pricing/payment options. That scope makes it distinguishable from narrower siblings like count_leads or list_industries, though no sibling is named explicitly.

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?

"Free, no account needed" implies this is a zero-cost first-look tool an agent can call before registering or buying, which is useful implied guidance. However, it never states when to prefer this over count_leads or preview_leads, nor does it set any preconditions or exclusions.

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