Skip to main content
Glama

ListHub – Japan B2B Sales List Quotes

件数と見積り

get_quote
Read-onlyIdempotent

地域×業種×項目(メール・フォーム・会社情報)の条件で、リストハブの営業リストの件数と税込金額、その条件の見積りページの URL を返します。金額は見積りページと同じ計算です。会社名や連絡先の中身は返しません。

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

Input Schema

NameRequiredDescriptionDefault
withNoこの項目がある会社だけに絞る。email=メールアドレス、form=お問い合わせフォームURL、president=代表者名、established=設立年、capital=資本金、employees=従業員数、sales=売上高。空なら絞らない(メール・フォームが無い会社も含む)。
areasNosearch_areas の候補の id。例:["北海道:札幌市"]、["北海道"]、全国なら ["all"]。複数選ぶと合計。
industriesNosearch_industries の候補の id。例:["big:飲食店"]、["mid:飲食店:居酒屋"]、["kw:ラーメン店"]。空なら全業種。

Output Schema

NameRequiredDescriptionDefault
okYes
countNo
errorNo
labelNo
priceNo
messageNo
order_urlNo
count_with_formNo
count_with_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the pricing matches the quote page calculation, and crucially it discloses what is NOT returned (company names and contact contents), which prevents a wrong expectation of the output. Return shape itself is covered by the output schema.

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

Conciseness5/5

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

Three tight sentences: what is returned first, then the pricing-equivalence note, then the negative scope. No filler, and the most important information (count, price, URL) is front-loaded.

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?

With three optional params, full schema coverage, an output schema, and complete annotations, the description only needs to frame the output and its limits, which it does. It falls short of full completeness by not connecting the area/industry id inputs to search_areas/search_industries or pointing to get_order_url as the follow-up step.

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%, and the schema already gives per-field meaning with examples for with, areas and industries. The description only restates the three condition axes (region × industry × item) without adding format, id-source, or edge-case detail beyond the schema, so the 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 uses a specific verb and resource: it returns the record count and tax-included price for a ListHub sales list under region × industry × item conditions, plus the quote page URL. It also bounds scope by stating that company names and contact details are not returned. It does not explicitly differentiate itself from the sibling get_order_url, which keeps it from 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 description implies this is the estimate/count step before ordering, and that the price matches the quote page, but it never states when to use this versus get_order_url or that search_areas/search_industries should be called first to obtain the area/industry ids. Usage is inferable but not spelled out.

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