Skip to main content
Glama
Sign In
freehire

freehire

by strelov1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

experience_add_achievement

Record a candidate's CV-bullet achievement as manual evidence so it can be cited on their CV. Re-adding an existing claim is refused, so update that entry instead.

Instructions

Record one piece of evidence — the sentence a CV bullet would carry. Only record what the CANDIDATE told you; the server stamps anything created here manual, which means they asserted it, and that stamp is what lets it be cited on a CV. A claim already in the bank, under any spelling, is refused as 409 rather than duplicated — so correct the existing one with experience_update_achievement instead of re-adding it.

Input Schema

NameRequiredDescriptionDefault
claimYesThe achievement as one CV-bullet-grade sentence.
skillsNoCanonical skill slugs, e.g. ["go", "kubernetes"].
contextNoHow it was done, in a sentence or two.
metricsNoNumbers as stated, e.g. ["20s->1s"].
employment_idNoThe place this belongs to; omit to leave it unplaced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the lone readOnlyHint=false annotation: it discloses the server-side `manual` provenance stamp and why it matters (CV citability), and documents the 409 duplicate-refusal behavior keyed on spelling. That is exactly the kind of side effect and failure mode an agent needs before calling.

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?

Three tight sentences, front-loaded with the core action before the provenance rule and the dedup/409 escape hatch. Slightly dense in the second sentence but no filler.

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?

Given full schema coverage and no output schema, the description covers purpose, provenance, and the duplicate case well. The only gap is that it doesn't say what a successful call returns (e.g., the created record id), which leaves a small amount for the agent to discover.

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 description coverage is already 100%, so the schema documents all five parameters. The description reinforces the `claim` semantics but adds nothing about skills, metrics, context, or employment_id beyond what the schema states; baseline 3 applies.

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?

Specific verb and resource ('Record one piece of evidence'), with the payload shape made concrete as 'the sentence a CV bullet would carry'. It is clearly distinguishable from the neighboring experience_update_achievement and experience_add_employment tools.

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 'only record what the CANDIDATE told you' constraint plus an explicit alternative: if the claim already exists, use experience_update_achievement instead of re-adding. Both the when and the when-not are stated.

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