Skip to main content
Glama

Data Candy: US business leads

Email a free sample

get_free_sample

Email 25 free real sample leads to an address (use the person's own email). This sends a real email. No text message is sent from here.

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": {
      "email": "<email>",
      "name": "<name>"
    },
    "name": "get_free_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the person asking for the sample.
emailYesWhere to email the sample: the person's own address.
phoneNoIgnored: no text message is sent from this tool.

Output Schema

NameRequiredDescriptionDefault
sentYes
emailYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds meaningful context on top by warning "This sends a real email" and clarifying that no text message is dispatched, which explains why the phone parameter is inert. It stops short of stating the non-idempotency consequence explicitly (repeat calls send repeat emails) or any rate/cost limits on the 25-lead sample.

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?

Two tight sentences, front-loaded with the core action, and the side-effect warning follows immediately. The closing sentence partly duplicates the phone parameter's schema description, a small redundancy but one that earns its place as an agent-safety cue.

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?

An output schema exists, so return values need not be explained, and the three parameters are fully covered. For an open-world, non-idempotent tool that fires a real outbound email, the main remaining gap is the absence of any note on repeat-call behavior or per-person sample limits.

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 100%, so the schema already documents name, email, and the ignored phone field. The description's "use the person's own email" restates the schema's own wording rather than adding format, format-validation, or edge-case meaning, so baseline 3 applies.

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 a specific action and resource with quantity and channel: email 25 free real sample leads to an address. An agent knows exactly what the call produces, though it never names a sibling (e.g. buy_leads or preview_leads) to sharpen the distinction between free sampling and purchasing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage constraint is a parameter-level one ("use the person's own email"); there is no statement of when to choose this over the many sibling lead tools such as preview_leads, quote_leads, or buy_leads. With eleven siblings in the namespace, the absence of routing guidance leaves the agent to infer selection from the tool name alone.

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