Skip to main content
Glama

Cover letter / 投稿信 Cover Letter

cover_letter

Cover letter / 投稿信 Cover Letter | USE WHEN: the user wants a cover letter to the journal editor | ALIASES: 投稿信, cover letter, 给编辑的信, 投稿说明 | RETURNS: 投稿信正文

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": {
      "title": "<title>",
      "target_journal": "<target_journal>"
    },
    "name": "cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes论文题目
abstractNo摘要
highlightsNo研究亮点
target_journalYes目标期刊

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, closed-world, non-read-only operation, so the safety profile is covered. The description adds only 'RETURNS: 投稿信正文', which is useful since there is no output schema, but it says nothing about length, language (Chinese vs English), tone, or whether the generated letter is saved anywhere versus just returned as text.

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 pipe-delimited format is front-loaded and scannable, with the trigger condition in the second slot where an agent will see it. The ALIASES segment and repeated bilingual title/name consume tokens without adding decision value, keeping it short of ideal.

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?

For a four-parameter, non-destructive generation tool with a fully documented schema and no output schema, the description covers purpose and return type adequately. It is still thin on how the optional inputs shape the result and on the expected output language/format, which matters for a bilingual tool.

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 every parameter carries a localized description, so the schema does the semantic work. The description mentions no parameters at all and does not explain how optional fields like abstract or highlights affect the output, which is the baseline for high-coverage schemas.

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 'USE WHEN' clause states the resource concretely: a cover letter addressed to the journal editor. The implied verb (generate/compose) is clear from the name and the RETURNS line, and it is distinguishable from siblings like academic_polish or deep_peer_review. It stops short of 5 because the operation itself is never stated with an explicit verb.

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 USE WHEN line gives one clear trigger condition, which is more than most definitions offer. However, it names no exclusions or alternatives (e.g., when to prefer academic_polish or citation_format instead), so the agent must infer boundaries between similar writing-assistance tools.

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