Skip to main content
Glama
seinun-ai

Maestro Career Studio

Official
by seinun-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Tailoring Session

get_tailoring_session
Read-onlyIdempotent

Fetch a tailoring session by ID to resume an unfinished gap walkthrough, check saved resolutions, and continue tailoring a resume.

Instructions

Fetch a tailoring session to resume a half-done gap walkthrough.

`tailoring_session_id` is the id returned by create_tailoring_session. Returns
the session with its frozen gap list (gaps_json), any resolutions saved so far
(resolutions_json), and status (open/tailored). resolutions_json may already
contain SYSTEM-PLANNED auto-resolutions stamped at creation (their payload
carries `provenance`, e.g. library_auto/kb_auto/kb_profile/wording_auto —
hand-made resolutions never do): verified evidence the resolver pre-applied.
To retract one, resend its gap_id with action "skip" via resolve_gaps.
Unresolved gaps are those in gaps_json with no entry in resolutions_json;
tailor_session consumes the saved resolutions. `base_anchors` are the base's
emphasis hints (countries, role, company, focus), not evidence; the anchor
company is the resume's own target, not necessarily this job's employer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tailoring_session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so safety is covered; the description adds real signal beyond them — the frozen gap list, that resolutions_json can carry pre-stamped SYSTEM-PLANNED auto-resolutions with provenance, and that tailor_session consumes the saved resolutions. It does not need auth/rate-limit detail for a safe read.

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?

Purpose is front-loaded and every sentence conveys domain-specific meaning, but the paragraph is dense with jargon and packs downstream usage (retraction, tailor_session consumption, base_anchors) into a single block that is harder to scan than it needs to be.

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 and no annotation detail on payloads, the description compensates by explaining the returned fields (gaps_json, resolutions_json, status) and the unresolved-gap definition. It is close to complete, missing only the exact status-transition or format conventions.

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 0%, so the description must carry the load for the single parameter, and it does: tailoring_session_id is explicitly defined as the id returned by create_tailoring_session. It does not state the string format, but the origin/linkage is the practically important information.

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 (fetch) and resource (tailoring session) plus intent (resume a half-done gap walkthrough). It is clearly distinguishable from create_tailoring_session, list_tailoring_sessions and close_tailoring_session among siblings.

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?

The 'to resume a half-done gap walkthrough' framing gives clear when-to-use context, and it names the producing tool (create_tailoring_session) and the consuming tool (tailor_session), plus resolve_gaps for retraction. It does not give explicit when-NOT-to-use or exclusion 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