Skip to main content
Glama

导出话题为 Markdown

app_export_session

Exports the full record of a specified session to a Markdown file and returns its content and save path for UI use.

Instructions

UI 专用:导出指定话题完整记录为 .md 文件并返回内容与保存路径。

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": {
      "sessionId": "<sessionId>"
    },
    "name": "app_export_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful behaviors beyond the schema: the tool writes a .md file to disk and returns the content plus the save path. It omits overwrite behavior, where the file is written, size limits, and error conditions.

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?

A single compact sentence with no wasted wording, front-loading the most decisive constraint ('UI 专用') before the action and its outputs.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers the essentials: what is exported, the output format, and that both content and save path are returned. Missing only file-location and overwrite details, which are minor at this complexity.

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 coverage is 0% for the single sessionId parameter, so the description must compensate. It only indicates that the argument identifies the '指定话题' to export, which adds minimal meaning beyond the parameter name and no format, source, or validation details.

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 uses a concrete verb + resource + output format: it exports '指定话题完整记录' (the full record of the given topic) as a .md file and returns both the content and the save path. This distinguishes it from read-only siblings such as app_get_state or app_get_diff, though it does not explicitly name any sibling.

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?

'UI 专用' (UI-only) signals the intended caller context and implicitly discourages direct agent invocation, but there is no explicit statement of when to prefer this over alternatives or any noted exclusions. Usage is implied rather than spelled out.

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