Skip to main content
Glama
JesusCabreraReveles

honest-cv

by JesusCabreraReveles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

log_application

Record or update a job application for a company and role. Track status changes, notes, and sent files.

Instructions

Record a job application, or update the one for the same company and role. Use it when the person sends a CV or letter, and whenever they tell you what happened (interview, offer, rejection); list_applications reads them back. Fields not given keep their value. Save the post's full text in post, since links expire, and your interview advice in prep. Each file in files is copied to /sent//, so the record keeps what was sent. Returns the application and not_found: paths it could not copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoLink to the job post.
dateNoDate of this status, YYYY-MM-DD. Default: today.
langNoLanguage of the CV sent.
postNoThe job post's full text, as the person gave it. Saved to <profile>/posts/.
prepNoWhat to prepare for the interview: skills to back with an example, gaps to explain, questions to ask. Replaces the list.
roleYesJob title, as in the job post.
filesNoPaths of the CV and letter sent. A copy is kept in <profile>/sent/.
notesNoContact person, salary range, next step... Added to the notes already there.
statusNoNew status: draft, applied, interview, offer, rejected or withdrawn. Each change is kept in the history with its date.
companyYesCompany name, as in the job post.
profileNoPath of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE).
variantNoVariant id of the CV sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • changedInput schema / properties / files / description
      Previous value: -"Paths of the CV and letter sent."New value: +"Paths of the CV and letter sent. A copy is kept in <profile>/sent/."
    • changedInput schema / properties / profile / description
      Previous value: -"Profile folder. Defaults to HONEST_CV_PROFILE."New value: +"Path of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE)."
    • changedInput schema / properties / status / description
      Previous value: -"New status. A change is kept in the history."New value: +"New status: draft, applied, interview, offer, rejected or withdrawn. Each change is kept in the history with its date."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=false) by disclosing merge semantics ('Fields not given keep their value'), a real side effect (each file is copied to <profile>/sent/<id>/), and the return payload including the not_found list. That is exactly the behavioral context an agent needs before mutating.

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 purpose and trigger, and every sentence carries information, but the middle is a dense run of embedded rationale and side-effect clauses rather than cleanly separated points.

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?

No output schema exists, yet the description explains what is returned (application and not_found), and it covers merge behavior, file side effects, and profile resolution for a 12-parameter mutation tool. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds rationale the schema lacks: save the post's full text because 'links expire', and use `prep` for interview advice. It leaves the remaining params (status, notes, variant, lang) to the schema.

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 and resource ('Record a job application') plus the upsert key ('or update the one for the same company and role'), which is the behavior an agent most needs to know. It also implicitly distinguishes itself from list_applications by noting that sibling 'reads them back'.

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 concrete triggers: 'when the person sends a CV or letter, and whenever they tell you what happened (interview, offer, rejection)'. It routes reads to list_applications, but offers no explicit when-not-to-use or prerequisite guidance.

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