Skip to main content
Glama

AceRound AI Interview Copilot

select_job_application_resume

Choose the resume for one application; pass resumeId null to go back to the base resume. Replies with the resume 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>",
      "resumeId": "<resumeId>"
    },
    "name": "select_job_application_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYesResume id, from list_resumes
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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that this is a mutation whose null case reverts to the base resume, that it echoes the resume back as confirmation, and that it requires the user's sign-in with the job_applications:write scope. It does not describe what happens to a previously selected resume when replaced, which keeps it short of full transparency.

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?

One compact sentence front-loads the action, then the null edge case, then the return behavior, with the auth requirement parenthetically separated. Every clause carries information; only 'as read back' is slightly awkward phrasing.

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?

With two required parameters, no output schema, and no nested objects, the definition covers the action, the null branch, an indication of the return value, and the auth scope. What remains thin is failure behavior (invalid or deleted resumeId) and any rate-limit or idempotency note, which are minor for a single-field setter.

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?

Schema coverage is 100% and both parameters are already documented with their source tools, so the schema carries the baseline. The description still adds meaning the schema does not: the schema only permits null via anyOf, while the description explains that null means 'go back to the base resume', which is the key semantic for that branch.

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: choose the resume for a single application, plus the exact effect of passing resumeId null (revert to base resume). The scope is unambiguous, but it does not name or contrast with any sibling tool, so an agent must infer boundaries from the name alone.

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 rather than spelled out: it is clear you call this to attach a resume (or detach one via null) for an existing application, and the required OAuth scope is disclosed. There is no explicit when-not guidance or pointer to alternative tools (e.g., resume management or application progress tools).

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