Skip to main content
Glama

AceRound AI Interview Copilot

mark_job_application_submitted

Destructive

Mark an application on the list as submitted (the user finished submitting on the employer site). Uses 1 Auto Apply credit if this one has not been charged yet; nothing while unlimited is active. Replies with the status as read back. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (Requires the user's sign-in with scope job_applications:write.)

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": {
      "applicationId": "<applicationId>"
    },
    "name": "mark_job_application_submitted"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesApplication id, from list_job_applications or the reply of an add-to-list tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare non-read-only, closed-world, and destructive; the description adds substantial context beyond that: one Auto Apply credit charged unless already charged, no charge while unlimited is active, returns the status read back, and requires a job_applications:write sign-in. The confirmation-before-charging requirement is exactly the kind of behavior an agent cannot infer from annotations.

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?

Purpose is front-loaded in the first sentence, with billing, return, and auth details following. It is dense and packs the auth scope into a trailing parenthetical, but no sentence is clearly wasted.

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

Completeness5/5

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

For a one-parameter state-transition tool with no output schema, the description covers cost, cost exemption, user consent requirement, auth scope, and what the reply contains. An agent has everything needed to call it safely and explain the consequence to the user.

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 the single applicationId parameter already documents its origin from list_job_applications or an add-to-list reply. The description adds no format or edge-case detail about the identifier, so baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Mark an application on the list as submitted") and clarifies the semantic event by defining it as the user having finished submitting on the employer site. That phrasing distinguishes it from siblings like mark_job_application_failed or an actual submission action.

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?

The precondition for calling it is stated clearly (the user finished submitting on the employer site), and it adds an operational gate: tell the user the cost and get agreement first. No explicit contrast with sibling tools, so it falls short of a 5.

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