Skip to main content
Glama

application_history

Read-only

Read application records and events to review past submissions, where simulated means no email was sent and sent means only that the SMTP service accepted it.

Instructions

读取投递记录与事件。simulated 代表没有发信,sent 仅表示 SMTP 服务接受。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "application_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description does not need to restate that. What it does add is genuinely useful: it defines the status vocabulary and warns that 'sent' only means SMTP acceptance rather than delivery. It still does not say what the result set covers (all applications versus a subset) or how it is ordered.

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?

There are two short sentences: the first states the purpose, and the second gives the semantic caveat. Each one earns its place, and there is no filler or repetition of the name or of annotation data.

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 parameterless read tool with no output schema, the main remaining question is what the result covers: all applications or one workspace, in what order, and how many records. The description clarifies status meaning but leaves that scope question unanswered, so it is adequate rather than complete.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 even though the description explains nothing about arguments. The status-value explanation it does include concerns the returned data rather than input parameters, and that explanation is a bonus rather than a substitute for parameter documentation.

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 specific verb (读取, "read") with a specific resource pair (投递记录, "application records" and 事件, "events"), so it is clearly a retrieval tool rather than an action tool like execute_application or prepare_application. It does not explicitly name a sibling to contrast with, which keeps it just 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 Guidelines3/5

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

The usage is implied: an agent would infer that this tool is for inspecting what happened to past submissions. However, the description never says when to prefer it over preview_application or execute_application, nor does it state prerequisites or scope limits.

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