Skip to main content
Glama
hermes-104-hunter

hermes-104-hunter

by HCH725

job104_get_my_templates

Retrieves saved 104 cover-letter templates for a job, including titles and content, enabling AI to match the user’s tone and draft customized recommendations without generic phrasing.

Instructions

讀取使用者 104 帳號中儲存的所有自薦信/求職信範本,包含範本標題與內文。供 AI 研讀並繼承使用者口吻,撰寫客製化推薦信時徹底消除 AI 罐頭感。

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": {
      "job_url_or_id": "<job_url_or_id>"
    },
    "name": "job104_get_my_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_url_or_idYes

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 carries the full burden, and '讀取' implies a read-only retrieval of all saved templates. However, it does not say whether an empty account returns an empty list, whether access requires the user's 104 login, or how large result sets are handled. It discloses the returned fields (titles and content), but that is largely 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.

Conciseness4/5

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

Two sentences, front-loaded with the resource and scope, followed by the intended use case. The phrase '徹底消除 AI 罐頭感' is promotional but still communicates the goal, so nothing is seriously wasted.

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 values need not be described. The remaining gap is the unexplained and seemingly contradictory required 'job_url_or_id' argument, which the description neither introduces nor justifies for a tool that claims to fetch all of the user's templates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents its single required parameter 'job_url_or_id' at 0% coverage, so the description must explain it — and it does not mention it at all. Worse, the description frames the tool as reading ALL templates in the user's account, which makes the required job identifier look unnecessary and leaves the agent guessing what value to supply.

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 states a specific verb and resource: reading all saved cover-letter/self-recommendation templates in the user's 104 account, including titles and body content. That is enough to separate it from siblings such as job104_search or job104_job_detail. It stops short of naming an alternative explicitly, 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?

Usage is implied rather than stated: '供 AI 研讀並繼承使用者口吻,撰寫客製化推薦信時' tells the agent this is for drafting customized cover letters in the user's voice. There is no explicit when-not guidance and no comparison with job104_prepare_application or job104_apply_analysis, so the agent must infer which tool fits a drafting workflow.

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