Skip to main content
Glama

AceRound AI Interview Copilot

get_job_application

Read-only

Show one Auto Apply application: job details (batch, type, description, requirements, deadline) and the resume used for it. (Requires the user's sign-in with scope job_applications:read.)

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": "get_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 already cover the safety profile (readOnly, non-destructive, closed-world), so the description adds real value by disclosing the required sign-in and the job_applications:read scope, plus the exact payload contents including the linked resume. It stops short of stating behavior for a missing or unauthorized applicationId.

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?

One front-loaded sentence delivers the resource and its returned fields, with the auth precondition isolated in a short parenthetical. No filler or redundant restatement of the tool name.

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 simple read-only, single-parameter tool with no output schema, the description is nearly complete: it lists the returned fields and states the auth requirement. Only the empty/error case is unaddressed, which is a minor gap at this complexity level.

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 100% and the single parameter already documents its own origin (from list_job_applications or an add-to-list reply). The description adds no further meaning about applicationId, so the baseline of 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?

The description gives a specific verb and resource ("Show one Auto Apply application") and enumerates what is returned: job details (batch, type, description, requirements, deadline) plus the resume. The singular "one" implicitly separates it from list_job_applications, but no sibling is named explicitly in the description itself.

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 only implied: it is obviously the detail view for a single application, and the auth scope signals the context. There is no explicit when-to-use guidance or steering away from alternatives such as preview_job_application_form or the mutation siblings (abandon, mark_submitted, etc.).

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