Skip to main content
Glama

AceRound AI Interview Copilot

restore_job_application

Restore a skipped application: never-submitted ones go back on the apply list, submitted ones go back to tracking (nothing is re-sent). Replies with the status as read back. (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": "restore_job_application"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds genuinely new context: state-dependent routing (apply list vs tracking), the assurance that nothing is re-sent, and the required auth scope job_applications:write. It does not explain failure modes (e.g. restoring an application that is not skipped) or whether progress data is preserved.

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?

Front-loaded with the action and its two outcomes, then the return behavior, then the auth requirement in a parenthetical. Both sentences carry distinct information and nothing is repeated from the schema or annotations.

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 mutation without an output schema, the definition covers the action, both outcomes, the non-resending guarantee, the return value, and the auth scope. Only edge cases, such as what happens when the application is not in a skipped state, are left unaddressed.

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?

Single parameter with 100% schema description coverage, so the schema already explains that applicationId comes from list_job_applications or an add-to-list reply. The description adds no additional meaning about the identifier beyond what the schema states, so baseline 3 applies.

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?

States a specific verb and resource ("Restore a skipped application") and immediately pins down the target population as skipped applications, which separates it semantically from abandon/remove siblings. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than declared.

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?

Usage is implied by the word "Restore" and by describing the two post-restore states, so an agent can infer when the tool applies. There is no explicit when-to-use versus abandon_job_application or remove_job_application, and no stated preconditions such as the application actually being in a skipped state.

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