Skip to main content
Glama

Data Candy: US business leads

Get an order

get_order
Read-onlyIdempotent

Check an order by its id: status (awaiting_payment, paid, fulfilled, expired ...), price and, once fulfilled, the first 25 leads plus download links for the whole set. Use it after a person has paid a checkout link. Nothing is charged.

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": {
      "order_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order id returned by buy_leads, like "ord_...". Keep it secret: it grants the download.

Output Schema

NameRequiredDescriptionDefault
kindNo
leadsYesAt most 25 leads, only when fulfilled. Use the download links for the full set.
notesNoPlain sentences from the API about this order, for example that the same search already has an unpaid order.
statusYesawaiting_payment, paid, fulfilled, expired, canceled, refunded or failed.
matchedNo
paid_atNo
currencyNo
downloadNo
livemodeNo
order_idYesThe order id. Keep it secret.
quantityNo
deliveredNo
next_stepYesWhat to do next, in plain words.
price_usdNo
created_atNo
expires_atNo
leads_shownYes
leads_totalYesHow many leads the order holds.
price_centsNo
checkout_urlNoOpen this page to pay (a person must do it).
next_after_idNo
payment_methodNo
leads_truncatedYesTrue when more leads exist than the 25 shown inline.
url_elicitationNoWhether the checkout link was also offered through URL-mode elicitation.
unit_price_centsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's "Nothing is charged" restates the safety profile rather than adding to it. What it does add beyond annotations is the state-dependent behavior: full leads and download links only appear once the order is fulfilled, and only the first 25 are returned inline.

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?

Three sentences, each doing work, with the return payload front-loaded and the usage hint kept to one clause. Minor bloat from enumerating statuses that the schema or output schema likely carries already.

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 single-parameter read with an output schema and safe annotations, this covers what the agent needs: what is returned, how fulfillment changes it, the 25-lead cap, and when to call. The remaining gaps are small, chiefly what happens for non-paid statuses.

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 the schema already documents the ord_ prefix, pattern, length bounds and the secrecy warning. The description repeats "by its id" without adding format or handling guidance, so the baseline of 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?

"Check an order by its id" names a specific verb and resource, and the sentence that follows spells out the payload: status values, price, and leads plus download links once fulfilled. It is clearly distinct from buy_leads or preview_leads, though no sibling is named outright.

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?

"Use it after a person has paid a checkout link" gives an explicit trigger condition that separates it from pre-purchase tools like preview_leads or quote_leads. It stops short of stating exclusions, e.g. what to call while the order is still awaiting_payment.

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