Skip to main content
Glama

TrueInterview

Score my résumé against a job

match_resume_to_job

Score the candidate's résumé against one job: match percentage, per-dimension scores, the reason and the skills they are missing. Give exactly one of job_id, application_id or job_description. Job pages are not fetched here: for a posting outside the catalog, read it yourself and pass its text as job_description. Uses their monthly AI allowance, and a score for a catalog job is saved on their board. Rewriting the résumé is not done here: tailor_url opens that on TrueInterview.

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": "match_resume_to_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo
application_idNo
job_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is not read-only, not destructive, not idempotent, and closed-world; the description adds the two facts an agent actually needs — it consumes a monthly AI allowance (cost) and a catalog-job score is persisted on the user's board (side effect). It also discloses a behavioral prerequisite the schema cannot express: the tool will not fetch job pages itself.

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?

Outputs, parameter rule, fallback behavior, cost, persistence, and the excluded capability all fit in four tight sentences with no filler. Information is front-loaded: what it returns first, then how to call it, then side effects.

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 no output schema, the description usefully enumerates the returned fields, and it covers cost and persistence for a non-read-only tool. It is slightly incomplete on identifier choice between job_id and application_id and on whether repeated calls re-charge the AI allowance, given idempotentHint is false.

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 description coverage is 0%, so the description must carry the parameters, and it names all three while conveying mutual exclusivity and the intended use of job_description. The remaining gap is that it never clarifies how job_id differs from application_id beyond the names, leaving the agent to guess which identifier a given context supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Score the candidate's résumé against one job') and enumerates the outputs: match percentage, per-dimension scores, reason, missing skills. It also explicitly separates itself from résumé rewriting by naming tailor_url, so an agent can distinguish it from tailor_resume.

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

Usage Guidelines5/5

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

States the selection constraint precisely ('Give exactly one of job_id, application_id or job_description') and gives the condition for the fallback: for a posting outside the catalog, read it yourself and pass its text. It also declares a clear out-of-scope case (rewriting) and points to the tool that does it.

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