Skip to main content
Glama
Sign In
Maestro Career Studio

Maestro Career Studio

Official
by seinun-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Career Context

get_career_context
Read-onlyIdempotent

Reads the user's career record as JSON or Markdown to ground career writing and outreach in approved resume points and memory notes, without inventing facts.

Instructions

Read the user's career record from the Career KB, as format="json" (the default) or format="markdown".

json: `resume`, the approved-points resume view assembled from the profile and the
non-archived entities, and `memory`, the beyond-the-resume string: identity facts and
entity notes that don't belong on a resume. `resume` carries approved points only;
`memory` also includes the profile summary and notes and the non-archived entities'
notes.

markdown: the exact portable career.md generated from the current Career KB, as
deterministic Markdown text, the file the web's career export downloads.

Intended as grounding for writing about the user's career (LinkedIn posts, outreach
drafts), optionally beside a base resume for its voice. It never invents facts,
metrics, employers, or dates; anything absent from it (and from a fetched base resume)
is not part of the user's recorded career. Neither format carries IDs; the profile
set's career history tools return the IDs needed to correct anything. Read-only.

Input Schema

NameRequiredDescriptionDefault
formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "enum": [
+    "json",
+    "markdown"
+  ],
+  "title": "Format",
+  "type": "string"
+}
  2. First observedv0.11.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent, but the description adds substantial non-redundant behavior: what 'resume' contains (approved points only), what 'memory' adds (profile summary, notes, non-archived entity notes), that markdown output is deterministic and matches the web export, and the critical constraint that neither format carries IDs. That last point materially changes how an agent would sequence calls.

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 the action and the format branch, then two clearly labelled per-format paragraphs. Slightly padded at the end — the 'never invents facts, metrics, employers, or dates' sentence is a useful grounding constraint but is stated at length, and the no-IDs point is repeated from context.

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?

There is no output schema, so the description must describe return contents — and it does for both formats, including what is excluded from 'resume'. Combined with the ID caveat and the grounding-use framing, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the enum values carry no descriptions, so the description must carry the burden — and it does. It documents both enum values, restates the default, and contrasts the two outputs semantically ('json' = assembled views, 'markdown' = exact portable career.md).

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 ('Read the user's career record from the Career KB') and immediately defines what the output is in each format. It is clearly distinguishable from siblings like kb_get_entity (single entity), kb_list_points (IDs), and get_base_resume (a different artifact).

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?

Explicitly frames intended use ('grounding for writing about the user's career... optionally beside a base resume for its voice') and routes correction work elsewhere ('the profile set's career history tools return the IDs needed to correct anything'). It stops short of naming that sibling tool or stating an explicit when-not-to-use case, so it's clear context without full exclusions.

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