Skip to main content
Glama

preview_application

Read-only

Displays the full application preview, including recipient, body, attachments, and digest, so a human can review and confirm it through the CLI before any email is sent.

Instructions

向用户完整展示收件人、正文、附件及 digest。确认由人工 CLI 完成,不能由模型自行生成批准。

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": {
      "id": "<id>"
    },
    "name": "preview_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context those annotations cannot: the output is meant for human inspection and the approval gate is out of the model's hands, which is the most important behavioral fact about this tool.

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 short sentences: the first states what is rendered, the second states the approval constraint. Nothing is wasted and the content description is front-loaded.

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 single-parameter read-only preview with no output schema, the description covers the key workflow constraint but omits the meaning of id and does not indicate the shape of what is displayed (e.g. whether the digest is a hash or a summary). Adequate but with a visible gap.

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?

There is one required parameter, id, with 0% schema description coverage, and the description never says what it identifies (an application? a draft? a batch?). With only one parameter a brief clause would have fully closed the gap, but the description leaves the schema to speak for itself.

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 concrete verb (完整展示 / fully display) and enumerates the resource payload (收件人、正文、附件及 digest), so an agent knows exactly what surfaces to the user. It does not explicitly contrast itself with nearby siblings such as prepare_application or execute_application, so it stops short of 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 Guidelines4/5

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

It gives a clear workflow rule: confirmation must happen through a human CLI and the model may not self-generate approval, which tells an agent how to act after calling it. It stops short of naming the drafting/execution siblings as the alternatives, so routing still requires inference.

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