Skip to main content
Glama
seinun-ai

Maestro Career Studio

Official
by seinun-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Restore Resume Version

restore_resume_version
Destructive

Restore a past resume or application snapshot into the live resume by kind, key, and version number, creating a new version without deleting history.

Instructions

Copy a past version's snapshot into the live resume.

Restore goes through the standard versioned write path — it is itself a
new version (history is append-only; nothing is deleted). kind/key as on
list_resume_versions: "base"+slug or "application"+id. For applications,
the old PDF is cleared; render_pdf produces a new one. A "base" restore
re-renders, so the response carries render_note (see render_pdf: non-null
only when a TeX-less backend rendered a LaTeX template through a Typst
one) and, if that render failed, render_error — the restore landed either
way, only the PDF is stale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
kindYes
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only flag destructive/not-idempotent; the description goes far beyond them by disclosing that history is append-only and nothing is deleted, that restoring an application clears the old PDF, and that a base restore re-renders with render_note/render_error while the restore still lands. This is exactly the kind of operational context annotations cannot convey.

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-loads the purpose in the first sentence, then layers the mechanism and edge cases. Dense but nearly every sentence adds a distinct fact; the render_note aside is slightly parenthetical but still load-bearing.

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?

With no output schema, the description responsibly explains the return values (render_note, render_error) and the failure semantics. The only gap is the 'number' parameter, which is left for the agent to infer.

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 0%, so the description must carry the burden. It clarifies kind/key ('base'+slug or 'application'+id), which covers two of three parameters, but leaves 'number' (the version to restore) unexplained beyond the vague 'past version's snapshot.' Partial compensation warrants a baseline 3.

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: 'Copy a past version's snapshot into the live resume.' An agent can immediately tell this apart from siblings like list_resume_versions or get_resume_version, which are reads rather than a restore.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It cross-references list_resume_versions to explain the kind/key convention, which helps the agent orient, but it never states when to prefer this over alternatives (e.g., edit_base_resume or duplicate_base_resume) or any preconditions/exclusions. Usage is implied rather than guided.

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