Skip to main content
Glama
hermes-104-hunter

hermes-104-hunter

by HCH725

job104_search

Search 104 job-bank listings by keyword with location conversion, minimum-salary filters, negotiable-salary exclusion, and remote-only options for targeted job discovery.

Instructions

搜尋 104 人力銀行職缺。支援地點中文轉換、薪資下限過濾、排除面議與完全遠端篩選,已進行三級 Token 清洗與精簡。

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": {
      "keyword": "<keyword>"
    },
    "name": "job104_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
pageNo
orderNo
keywordYes
page_sizeNo
min_salaryNo
remote_onlyNo
exclude_negotiableNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral burden, and it does disclose one meaningful trait: results have been token-cleaned and trimmed ('三級 Token 清洗與精簡'), warning the agent that returned fields may be condensed. However, it never covers pagination behavior, result ordering, error conditions, or read-only characteristics, so major gaps remain.

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?

Two sentences, purpose front-loaded, then a dense feature clause with no filler. The trailing token-cleaning note is slightly implementation-flavored but earns its place by signaling trimmed output.

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

Completeness3/5

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

An output schema exists, so return-value documentation is not needed, but an 8-parameter tool at 0% schema coverage needs more than four loosely named capabilities. Missing: ordering semantics, pagination limits, and guidance on following up with job104_job_detail.

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% across 8 parameters, so the description must compensate, and it partially does: area accepts Chinese location names with conversion, min_salary is a lower bound, exclude_negotiable drops 面議 postings, and remote_only restricts to fully remote roles. keyword, page, page_size, and especially order (unclear whether it's a sort or filter) remain 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 a specific verb and resource: '搜尋 104 人力銀行職缺' (search 104 job-bank openings), which an agent can immediately distinguish from the sibling tools that fetch details, analyze applications, or prepare submissions. It does not explicitly name those siblings as alternatives, 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 Guidelines2/5

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

The description only lists supported search features; it gives no guidance on when this tool should be used instead of job104_job_detail or job104_prepare_application. It also says nothing about prerequisites, when not to call it, or how to chain it into detail retrieval.

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