Skip to main content
Glama

execute_application

Destructive

Send or validate a job application email: dryRun checks only, while false sends after manual digest confirmation and environment enablement; prevent resends when outcome is unclear.

Instructions

dryRun 必填:true 仅检查,不发信;用户要求真实投递时用 false。实际发送需要环境开关和对应 digest 的人工确认。结果不明确时禁止重发。

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>",
      "dryRun": "<dryRun>"
    },
    "name": "execute_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dryRunYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely useful context: real sending is gated behind an environment switch plus manual confirmation of a corresponding digest, and duplicate sends are forbidden when results are ambiguous. That is meaningful disclosure of side effects and operational constraints beyond what annotations provide, though it still doesn't say exactly what state is mutated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loads the most safety-critical fact (dryRun semantics), which is good. But it is terse to the point of under-specification: it spends all its words on the flag and none on the tool's own purpose, so density is not matched by coverage.

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

Completeness2/5

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

For a destructive, open-world execution tool with no output schema and 0% schema description coverage, the definition should establish what is executed, what the id refers to, and what 'digest confirmation' means in practice. It covers the dryRun safety path and the resend hazard but leaves the core action and one required parameter unexplained, so an agent cannot call it confidently.

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 0%, so the description must carry the load. It fully explains dryRun (required, true = check only, false = real send), which is good, but the required 'id' parameter is never explained at all — the agent doesn't know whether it identifies an application, a digest, or a job. Half the parameters remain semantically opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool actually does in verb+resource terms; it only discusses the dryRun switch and the hazards of sending. The agent must infer from the name and the phrase '实际发送' that this submits/executes an application, and must guess what is being sent (an email? an application submission?) and which 'digest' must be confirmed. Siblings like preview_application and prepare_application are never contrasted, so the boundary is unclear.

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?

It gives actionable conditional guidance for the dryRun flag (true = check only, false = real delivery when the user asks for it) and an explicit prohibition on resending when the outcome is unclear. However, it gives no guidance on when to pick this tool over preview_application or prepare_application, and no prerequisites beyond a vague 'environment switch'.

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