HokAI

buy_leads

Buy 1 to 20 Hokai buyer leads. A lead is a person who told Smart Match the
job, the tools they use and often the budget, then agreed to hear from
vendors (three vendors per buyer at most). Returns checkout_url, a Stripe
card payment page.

Rule to pass on to the vendor: leads are delivered as buyers who fit come
in. There is no stock cap: the balance never expires and one lead is used
each time a buyer's brief is opened. Every purchase includes a year of
Premium. Refunds are not automatic: ask damien@hokai.io.

Args:
    email: a work email for the vendor
    quantity: 1 to 20
    company: company name (optional)
    agent: your agent's name (optional)

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>",
      "quantity": "<quantity>"
    },
    "name": "buy_leads"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	No
`email`	Yes
`company`	No
`quantity`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call returns a Stripe checkout_url, that the lead balance never expires, that one lead is consumed per brief opened, that Premium is bundled, and that refunds require emailing damien@hokai.io. It leaves one meaningful gap: whether invoking the tool charges the card or only creates a payment link.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence and the args block are efficient, but the middle paragraph mixes binding rules with marketing copy ('Every purchase includes a year of Premium') and buries the refund caveat at the end. Front-loading the checkout_url return and trimming pitch language would tighten it.

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 four-parameter purchase tool with no output schema and no annotations, the description covers the return value, consumption model, refund path, and all parameters. The remaining ambiguity around immediate charge vs. link-only is the notable hole.

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 0%, so the description must compensate, and it does: email is the vendor's work email, quantity is 1-20, company and agent are marked optional. Only minor format expectations (email validation, agent naming) are left unspecified.

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 a specific verb ('Buy') and resource ('Hokai buyer leads') with a concrete quantity range of 1-20, and defines what a lead is. It does not explicitly contrast with siblings like buy_listing or buy_guide_spot, so it stops short of a 5.

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 vendor-facing framing ('Rule to pass on to the vendor') implies the audience and context, but there is no explicit when-to-use/when-not guidance or named alternative tools for purchasing other products. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HokAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?