Skip to main content
Glama

Regenerate resume feedback

refreshResumeFeedback

Generate fresh AI feedback on the candidate's primary resume. It runs in the background for about a minute; call listResumes afterwards to read it. Needs at least one resume on file.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "refreshResumeFeedback"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
runIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Adds behavior the annotations cannot express: the work happens asynchronously, takes roughly a minute, must be polled via listResumes, and requires existing resume data. The privacy/usage-tracking note also discloses data handling. It does not say whether re-running replaces prior feedback or incurs cost, which is the main remaining gap for a non-idempotent generation call.

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?

Three short sentences with the action front-loaded, followed by the async/follow-up constraint and the prerequisite. Nothing is padded; even the data-handling line is a single compact sentence.

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?

An output schema exists, so return shape need not be explained. Given a zero-parameter, non-destructive generation call, the description covers prerequisite, timing, and how to retrieve the result — everything needed to invoke it correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the implicit target ('primary resume'). The baseline for a no-parameter tool 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: 'Generate fresh AI feedback on the candidate's primary resume.' The scope ('primary resume') is precise enough that an agent knows exactly which artifact is affected. It does not explicitly contrast with other feedback/analysis siblings, so it stops short of a 5.

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?

Gives a real prerequisite ('Needs at least one resume on file') and an explicit follow-up path ('call listResumes afterwards to read it'), which is exactly the guidance an agent needs to sequence calls. It does not state when not to call it or name an alternative for already-generated feedback, so it is clear context rather than full routing.

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