Skip to main content
Glama
Sign In
freehire

freehire

by strelov1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cv_edit

Apply path-addressed batch edits to a tailored CV atomically, rejecting the whole batch if any claim lacks evidence. Review cv_context and cv_get first; export with cv_render.

Instructions

Apply a batch of path-addressed edits to a tailored CV, atomically. Read cv_context and cv_get first — indices are counted over the document cv_get returned. THE HONEST WALL: editing with an API key edits as the tailoring agent, and the server enforces it — the candidate's own name, email, phone and links are refused, and anything stating what they DID needs evidence_id, the id of something they asserted themselves. One uncited op rejects the whole batch. For a missing_have requirement, reframe an existing bullet; for a missing_gap, ask the candidate before writing anything. A bad path is a 422 and the CV is untouched. Export with cv_render.

Input Schema

NameRequiredDescriptionDefault
idYesThe CV id, from cv_tailor or cv_list (or the tailoring workspace URL /tailor/<job>?cv=<id>). Opaque — never construct or guess one.
opsYesEvery edit that belongs together, in one call.
noteNoYour own one-line reason for the change; shown to the candidate as the agent's words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the load and does so richly: atomicity ('one uncited op rejects the whole batch'), server-enforced refusal of PII fields, the evidence_id requirement, and the 422-on-bad-path contract with the CV left untouched.

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?

Front-loaded with the core action and prerequisite, then the constraint wall, then the escape hatch (cv_render). The 'THE HONEST WALL' framing is stylized but the content under it is dense and non-redundant; a slightly cleaner register would earn a 5.

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?

For a mutation tool with no output schema, it covers prerequisites, error semantics, and the evidence contract well. It does not say what a successful batch returns (result shape, counts, whether a new CV revision id comes back), which is the one gap given no output schema exists.

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%, so a baseline 3 applies, but the description adds genuine meaning beyond the schema: it explains that path indices are counted over the document cv_get returned and reinforces that evidence_id backs any claim of what the candidate did. The note parameter is not elaborated, which keeps it short of a 5.

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?

States a specific verb (apply a batch of edits), resource (tailored CV), and a distinguishing trait (path-addressed, atomic). An agent can differentiate it from cv_tailor, cv_get, and experience_* tools immediately.

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?

Explicit prerequisites (read cv_context and cv_get first, because indices are counted over cv_get's output), a routing rule for missing_have vs missing_gap, and a pointer to cv_render for export. Alternatives and conditions are named rather than inferred.

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

Deploy Server

Other Tools