Skip to main content
Glama

tailor resume to job

tailor_resume_to_job
Read-only

Tailor a resume to a job description with ATS keyword-match analysis, write a cover letter, or prepare for interviews, using LittlePinkPotato on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

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

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

With readOnlyHint and openWorldHint already given, the annotations carry the safety profile; the description usefully adds that the return includes the agent description, price, free runs, run link and a ready-to-send request. However, the front-loaded 'Tailor a resume...' framing implies the tool executes the work, which sits awkwardly against readOnlyHint=true, and the ordering invites misreading before the clarification arrives.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, but the structure is inverted: the misleading capability claim leads and the actual return behavior, which is what an agent most needs, trails at the end. Reordering the same content would materially improve selection accuracy.

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?

There is no output schema, and the description does the minimum by enumerating return fields, which is the key gap it needed to fill. It omits what the caller should do with the 'ready-to-send request' and whether invoking the agent costs anything beyond the mentioned free runs, leaving the end-to-end flow underspecified.

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 optional 'task' parameter is fully documented in the schema, so the schema does the work here. The description adds no detail about what the task string should contain or how it influences the returned request.

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

Purpose3/5

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

The description names a concrete resource and three concrete capabilities (resume tailoring with ATS keyword matching, cover letter, interview prep), but its opening reads as if the tool performs that work, while the closing sentence reveals it only returns agent metadata plus a ready-to-send request. It never distinguishes itself from the near-identical sibling get_finch_agent, so an agent cannot tell which one 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?

Listing three task scenarios hints at when the tool applies, but there is no explicit condition for choosing it over get_finch_agent, search_finch_agents, or how_to_call_finch_agents, all of which appear to cover the same discovery-and-invoke flow. No when-not-to-use guidance and no mention of what happens after the request is returned.

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.