Skip to main content
Glama
JesusCabreraReveles

honest-cv

by JesusCabreraReveles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

checklist_new

Write a merged, prefilled checklist file for users with many skills to mark in their editor, then call checklist_apply. Prevents duplicates; won't replace existing files unless overwrite is allowed.

Instructions

Write a checklist file for the person to mark in their editor, merged from the templates picked in checklist_list, without duplicates and prefilled from the inventory. Use it when the person has many skills: it is much faster than asking one by one. Next step: once they have marked it, call checklist_apply. Refuses to replace an existing file unless overwrite. lists may be empty when extra names the skills. Returns the file's path and its number of skills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoThe person's language: the file's headings and the built-in templates in it.en
pathNoFile to write. Default: <profile>/checklist.md.
extraNoMore skill names to ask about, e.g. found in an imported profile.
listsYesIds from checklist_list, e.g. backend-jvm, or paths to .md templates.
profileNoPath of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE).
overwriteNoReplace the file if it exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.2
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "en",
+  "description": "The person's language: the file's headings and the built-in templates in it.",
+  "enum": [
+    "en",
+    "es"
+  ],
+  "title": "Lang",
+  "type": "string"
+}
    • 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)."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Discloses behavior beyond annotations: refuses to replace an existing file unless overwrite is set, dedupes templates, prefills from inventory, and returns path plus skill count. Annotations only cover the safety triad, so these are genuine additions. Minor gap: no info on whether a partial read/write or permissions are involved.

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?

Compact and front-loaded with purpose, then usage, then next-step, then behavioral guarantees. Slightly dense with three ideas packed into single sentences, but no waste.

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?

Covers purpose, workflow position, cross-parameter interaction, refusal behavior, and return value despite no output schema. Nearly complete for a file-producing tool; only missing error/edge-case behavior.

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%, so the schema already documents all six parameters with defaults and the lang enum. The description only adds that lists may be empty when extra supplies skills, a useful cross-parameter constraint but otherwise baseline.

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 ('Write a checklist file... merged from the templates picked in checklist_list') and distinguishes itself clearly from siblings by naming checklist_list as its upstream source and checklist_apply as its downstream step.

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?

Explicitly gives the when-to-use condition ('Use it when the person has many skills: it is much faster than asking one by one') and names the alternative workflow (asking one by one), then routes to the next tool (checklist_apply).

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