Skip to main content
Glama

CareerProof MCP

by ai.careerproof.mcp
OverviewDiscussionsAdmin

ceevee_get_positioning_session

Read-onlyIdempotent

Get full positioning session detail including analysis, lens, opportunities, targeted edits, and PDF download URLs. session_id from ceevee_list_positioning_sessions or from ceevee_analyze_positioning response. Contains everything generated across the analyze -> opportunities -> confirm-lens pipeline. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession ID from ceevee_list_positioning_sessions or ceevee_analyze_positioning response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
created_atNo
edits_jsonNo
updated_atNo
session_nameNo
analysis_jsonNo
current_stageNo
cv_version_idNo
confirmed_lensNo
cv_version_nameNo
is_quick_reviewNo
clean_pdf_base64No
review_pdf_base64No
custom_positioningNo
opportunities_jsonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedOutput schema / properties / analysis
      Removed value: -{
-  "anyOf": [
-    {},
-    {
-      "type": "null"
-    }
-  ]
-}
    • addedOutput schema / properties / analysis_json
      Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / clean_pdf_base64
      Added value: +{
+  "$ref": "#/properties/session_name"
+}
    • changedOutput schema / properties / confirmed_lens / $ref
      Previous value: -"#/properties/status"New value: +"#/properties/session_name"
    • changedOutput schema / properties / created_at / $ref
      Previous value: -"#/properties/status"New value: +"#/properties/session_name"
    • addedOutput schema / properties / current_stage
      Added value: +{
+  "$ref": "#/properties/session_name"
+}
    • addedOutput schema / properties / custom_positioning
      Added value: +{
+  "$ref": "#/properties/session_name"
+}
    • addedOutput schema / properties / cv_version_name
      Added value: +{
+  "$ref": "#/properties/session_name"
+}
    • removedOutput schema / properties / detected_lens
      Removed value: -{
-  "$ref": "#/properties/analysis"
-}
    • removedOutput schema / properties / edits
      Removed value: -{
-  "$ref": "#/properties/analysis"
-}
    • addedOutput schema / properties / edits_json
      Added value: +{
+  "$ref": "#/properties/analysis_json"
+}
    • addedOutput schema / properties / is_quick_review
      Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • removedOutput schema / properties / opportunities
      Removed value: -{
-  "$ref": "#/properties/analysis"
-}
    • addedOutput schema / properties / opportunities_json
      Added value: +{
+  "$ref": "#/properties/analysis_json"
+}
    • removedOutput schema / properties / pdf_urls
      Removed value: -{
-  "$ref": "#/properties/analysis"
-}
    • addedOutput schema / properties / review_pdf_base64
      Added value: +{
+  "$ref": "#/properties/session_name"
+}
    • addedOutput schema / properties / session_name
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / status
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedOutput schema / properties / updated_at / $ref
      Previous value: -"#/properties/status"New value: +"#/properties/session_name"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the cost trait ('Free') and notes it is a consolidated superset read, which is genuine added context, but it says nothing about auth, pagination, or size/rate limits.

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 return contents and kept to three short sentences. The third sentence ('Contains everything generated across the analyze -> opportunities -> confirm-lens pipeline') partially repeats the contents list already given, costing a little redundancy.

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 an output schema present, return values need not be explained, and the annotations carry the safety profile. The description covers purpose, contents, and parameter provenance adequately; only explicit alternative-routing guidance is missing.

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%, so the single session_id parameter is fully documented in the schema. The description repeats the same provenance guidance without adding type, format, or validation meaning beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (positioning session detail), then enumerates the contents: analysis, lens, opportunities, targeted edits, and PDF URLs. The pipeline-superset phrasing distinguishes it from the narrower step tools like ceevee_get_opportunities, though no sibling is named directly.

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?

Useful provenance guidance: session_id comes from ceevee_list_positioning_sessions or the ceevee_analyze_positioning response. However, there is no explicit when-to-use vs ceevee_get_opportunities or ceevee_confirm_lens, so routing must be inferred from the 'everything in the pipeline' phrasing.

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

All CareerProof MCP toolsInspect
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