CareerProof MCP

ceevee_get_version

Read-onlyIdempotent

Get detailed CV version including structured content, sections, word count, and audience profile. cv_version_id from ceevee_upload_cv or ceevee_list_versions. Use to inspect CV content before running analysis tools. Free.

Input Schema

Name	Required	Description	Default
`cv_version_id`	Yes	CV version ID from ceevee_upload_cv or ceevee_list_versions

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	No
`status`	No
`is_main`	No
`user_id`	No
`created_at`	No
`edit_count`	No
`updated_at`	No
`career_path`	No
`description`	No
`document_id`	No
`seniority_level`	No
`content_snapshot`	No
`years_experience`	No
`parent_version_id`	No
`audience_confidence`	No
`audience_profile_label`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 5, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / audience_confidence

Added value: +{
+  "$ref": "#/properties/user_id"
+}

removedOutput schema / properties / audience_profile

Removed value: -{
-  "$ref": "#/properties/sections"
-}

addedOutput schema / properties / audience_profile_label
```
Added value: +{
+  "$ref": "#/properties/name"
+}
```

addedOutput schema / properties / career_path

Added value: +{
+  "$ref": "#/properties/name"
+}

addedOutput schema / properties / content_snapshot

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / created_at / $ref

Previous value: -"#/properties/filename"New value: +"#/properties/name"

addedOutput schema / properties / description

Added value: +{
+  "$ref": "#/properties/name"
+}

addedOutput schema / properties / document_id

Added value: +{
+  "$ref": "#/properties/user_id"
+}

addedOutput schema / properties / edit_count

Added value: +{
+  "$ref": "#/properties/user_id"
+}

removedOutput schema / properties / filename

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / name

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / parent_version_id

Added value: +{
+  "$ref": "#/properties/user_id"
+}

removedOutput schema / properties / sections

Removed value: -{
-  "anyOf": [
-    {},
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / seniority_level

Added value: +{
+  "$ref": "#/properties/name"
+}

addedOutput schema / properties / status

Added value: +{
+  "$ref": "#/properties/name"
+}

addedOutput schema / properties / updated_at

Added value: +{
+  "$ref": "#/properties/name"
+}

addedOutput schema / properties / user_id

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

removedOutput schema / properties / word_count

Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}

addedOutput schema / properties / years_experience

Added value: +{
+  "$ref": "#/properties/user_id"
+}

First observedMar 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds two traits annotations don't carry: the cost ('Free') and the shape of what's returned (structured content, sections, word count, audience profile). Missing only details like whether all content is returned vs. truncated.

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 short sentences, all front-loaded with the purpose and then usage. Minor redundancy between the description's ID provenance sentence and the schema's own description, but nothing wasteful overall.

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?

Output schema exists, so return values need not be spelled out, and annotations cover the safety profile. The description still adds the useful pre-analysis workflow cue and cost note, leaving little an agent would need that isn't already covered.

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 100% and the single parameter is fully documented. The description's provenance note ('cv_version_id from ceevee_upload_cv or ceevee_list_versions') repeats the schema wording verbatim, adding no new semantic detail, so 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?

States a specific verb ('Get') and resource ('CV version') and enumerates the returned payload (structured content, sections, word count, audience profile). This clearly distinguishes it from the sibling ceevee_list_versions, which only enumerates versions.

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?

'Use to inspect CV content before running analysis tools' gives explicit workflow context and ordering. It names the source tools for the ID, but no explicit exclusions or alternatives beyond the implied list-vs-get split.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CareerProof MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?