Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

hk-talent.talent_quota

Read-onlyIdempotent

Ask "how hard is it to get a Hong Kong talent visa" — free: 2025 total applications and approvals across all schemes. | 免费档:2025 年各项人才入境计划的合计申请量 / 获批量 / 有数据计划数(只给总数,不给任何单个计划);单计划两年明细走 approval_analysis。

[zh] 供应方资产「香港人才入境计划官方统计(2024-2025)」免费(每日限额按调用方计)。 入参:无。 [en] Vendor asset "香港人才入境计划官方统计(2024-2025)". Free (daily per-caller quota). Args: none. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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-talent.talent_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / plan
      Removed value: -{
      -  "title": "Plan",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "plan"
      -]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, but the description adds real value beyond them: a daily per-caller free quota, the explicit limit that only totals are returned with no individual scheme data, and where payment credentials must go (X-Payment / X-Payment-Tx / Authorization headers, not parameters). It stops short of describing response shape or what happens on quota exhaustion, so it is strong rather than complete.

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?

The lead sentence front-loads the purpose and the routing hint in one line, which is the most important content. It loses a point for the duplicated bilingual blocks — the vendor-asset and free-quota statements say essentially the same thing in Chinese and English — plus a second restatement of the free tier in the first line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema aggregate query, the description supplies everything an agent needs: what is returned (total applications, approvals, count of schemes with data), what is deliberately excluded (per-scheme figures), the cost/quota model, and the auth header convention. There is no meaningful gap left for correct invocation.

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?

The tool takes zero parameters and the description confirms this explicitly ("入参:无 / Args: none"), which matches the empty schema. No further parameter meaning is needed or possible, so the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb and resource — 2025 total applications and approvals summed across all talent schemes — and frames it around the real user question ("how hard is it to get a Hong Kong talent visa"). It explicitly contrasts with the sibling approval_analysis, which gives per-scheme two-year detail, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

States when to use it (aggregate difficulty question, totals across all schemes, free tier) and when not to (any per-scheme or multi-year breakdown → approval_analysis). The free-tier/daily-quota note also signals it is the cheap first-stop option.

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.