Skip to main content
Glama
hk-ipo-fee-mcp

hk-ipo-fee-mcp

hk_listings

Retrieve Hong Kong company listings with Wikidata listing dates, newest first, and filter by since/until dates; recent IPO coverage is incomplete and IPO terms are excluded.

Instructions

HK listings with a listing date in Wikidata (CC0), newest first; since/until are YYYY-MM-DD. Coverage of recent IPOs is incomplete; IPO terms are NOT included.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
untilNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 disclose useful traits: the upstream source and licence (Wikidata CC0), the default sort order, and a data-quality caveat about incomplete recent-IPO coverage. What is missing is whether results are paginated or truncated by limit and whether the call has any side effects (implied read-only by 'listings' but not stated).

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?

Two tight sentences: the identity, source and ordering come first, then the date-format rule and the coverage caveat. Every clause carries information an agent would otherwise have to guess.

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 three-parameter read tool with an output schema (so return values need not be described), this covers identity, ordering, date formats and data caveats. The remaining gap is limit behavior, which matters because callers will want to know if 30 is a ceiling.

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 0%, so the description must compensate and it partly does by specifying that since/until take YYYY-MM-DD. The limit parameter is untouched — no indication of whether it is a page size, a cap, or what happens above the default of 30 — leaving one of three parameters undocumented anywhere.

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 resource precisely (HK listings that have a listing date in Wikidata), states the ordering (newest first) and the data source/licence (CC0). It is not just a restatement of the name, and the explicit note that IPO terms are excluded separates it from the hk_ipo_* siblings, though it never says which sibling to use instead.

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?

"Coverage of recent IPOs is incomplete; IPO terms are NOT included" implies that IPO-term questions belong to hk_ipo_rules / hk_ipo_plan etc., but the routing is left to inference rather than stated. No explicit when-to-use or when-not-to-use condition is given.

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