Skip to main content
Glama

get_resume_insights

Read-onlyIdempotent

Retrieve skill gaps, strengths, and improvement suggestions from a saved resume by ID, with optional LLM reasoning to guide resume updates and job matching.

Instructions

Get resume skill gaps, strengths, and suggestions with optional client LLM reasoning.

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": {
      "id": "<id>"
    },
    "name": "get_resume_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInternal integer ID of saved resume in local SQLite database (returned by analyze_resume)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / id / description
      Added value: +"Internal integer ID of saved resume in local SQLite database (returned by analyze_resume)"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one behavioral detail, an 'optional client LLM reasoning' mode, but leaves that jargon unexplained — no cost, latency, or determinism implications are stated, and no indication of which fields change when that option is used.

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 front-loaded sentence with no padding; the returned content leads and the modifier trails. The only weakness is that the trailing 'optional client LLM reasoning' clause is vague rather than informative.

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

Completeness3/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 values need not be described, and the tool is a simple single-parameter read. Still, the presence of get_resume_insights_advanced plus an unexplained optional reasoning mode means the definition is not quite complete enough for confident selection.

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?

There is a single parameter at 100% schema coverage, and the schema already explains that it is the internal SQLite resume ID returned by analyze_resume. The description adds nothing about the parameter, so the baseline 3 for high-coverage schemas 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 ('Get') and enumerates the resource returned: skill gaps, strengths, and suggestions. It is clear what the tool produces, but it never names or contrasts with the sibling get_resume_insights_advanced, so an agent cannot tell from the text which of the two to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no exclusions. With a near-identical sibling (get_resume_insights_advanced) and a related producer (analyze_resume), omitting any routing rule leaves selection entirely to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.