Skip to main content
Glama
JesusCabreraReveles

honest-cv

by JesusCabreraReveles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

checklist_list

Read-only

Lists skill checklist templates so people can choose ones matching their profession before creating a checklist. Includes titles, descriptions, skill counts, and origins; supports English and Spanish.

Instructions

List the skill checklist templates the person can combine. Use it before checklist_new, to let the person pick the ones that fit their profession. Returns checklists: each with its id, title, description, number of skills and origin ("built-in", or "yours" for templates in /checklists/). Any profession works. Pass lang in the person's language to get the translated templates. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoThe person's language: the built-in templates in it, where translated.en
profileNoPath of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE).

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 built-in templates in it, where translated.",
+  "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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the trailing 'Read-only' restates structured data and adds nothing. However, the description goes beyond the annotations by disclosing the return payload (checklists with id, title, description, skills count, origin) and the origin semantics ('built-in' vs 'yours' for templates in <profile>/checklists/), which is genuinely useful behavior detail.

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, then usage, then return shape — a sensible ordering. Slightly dense, and the closing 'Read-only' is redundant with annotations, but no sentence is wasted overall.

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 enumerates the returned fields and the origin values, so an agent knows exactly what it will receive. Combined with the routing guidance to checklist_new, nothing needed to call this 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. The description still adds meaning by explaining why lang matters ('Pass `lang` in the person's language to get the translated templates'), which clarifies the translation behavior of that parameter beyond the schema's terse wording.

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 ('List the skill checklist templates') and immediately qualifies scope ('the person can combine'), which separates it from checklist_new, checklist_apply and the other checklist siblings. An agent can identify what this does without opening the schema.

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?

Gives explicit sequencing guidance ('Use it before checklist_new, to let the person pick the ones that fit their profession'), naming the alternative tool and the condition that selects it. It also clarifies applicability ('Any profession works'), removing a common hesitation point.

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