CareerProof MCP

atlas_create_jd

Create a job description from text within a hiring context. Returns a JD object with 'id' and stored content. Use JD content as jd_text in atlas_fit_match, atlas_fit_rank, atlas_start_jd_fit_batch, and atlas_start_jd_analysis. Requires context_id from atlas_create_context or atlas_list_contexts. Free.

Input Schema

Name	Required	Description
`title`	Yes
`content`	Yes	Full JD text
`context_id`	Yes	Context ID from atlas_create_context or atlas_list_contexts

Output Schema

Name	Required	Description	Default
`id`	Yes
`title`	Yes
`source`	No
`content`	No
`user_id`	No
`file_type`	No
`created_at`	No
`is_default`	No
`updated_at`	No
`analysis_result`	No
`last_analyzed_at`	No
`client_context_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 5, 2026

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

addedOutput schema / properties / analysis_result

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

addedOutput schema / properties / client_context_id

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

addedOutput schema / properties / file_type

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

addedOutput schema / properties / is_default

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

addedOutput schema / properties / last_analyzed_at

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

addedOutput schema / properties / source

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

addedOutput schema / properties / updated_at

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

addedOutput schema / properties / user_id

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

First observedMar 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so safety is covered. The description adds one useful non-annotation fact ('Free'), but omits that repeated calls create duplicates (idempotentHint=false) and says nothing about permissions or mutation side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action, then output shape, then downstream usage, then prerequisite and cost. No filler; each sentence carries distinct information.

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?

An output schema exists, so return-value detail is not required, and the description still summarizes the return. It covers creation, prerequisites, and consumers, but leaves minor behavioral gaps such as duplicate-title handling and whether content is stored verbatim or parsed.

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 67%: 'content' and 'context_id' are documented in the schema, and the description only repeats the context_id provenance rather than adding new meaning. Beyond 'from text' there is no guidance on expected content format, length, or title conventions, so it is baseline-adequate but no more.

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 ('Create a job description from text'), scopes it to a hiring context, and names the returned artifact ('JD object with id and stored content'). An agent can immediately distinguish it from atlas_list_jds or the fit-match siblings.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite (context_id from atlas_create_context or atlas_list_contexts) and the downstream routing ('Use JD content as jd_text in atlas_fit_match, atlas_fit_rank, atlas_start_jd_fit_batch, and atlas_start_jd_analysis'). This tells the agent both how to obtain inputs and where the output flows next.

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?