CareerProof MCP

atlas_create_context

Create a new hiring context (company profile) for organizing candidates and JDs. Returns a context object with 'id'. Use this id as context_id in atlas_upload_candidate, atlas_create_jd, atlas_list_candidates, and all analysis/batch/utility tools. This is the first step in the Atlas workflow. Free.

Input Schema

TableJSON Schema

Name	Required	Description
`industry`	No
`location`	No
`is_default`	No
`company_name`	Yes
`company_size`	No
`hiring_context`	No	Hiring context details (open roles, budget, goals)
`company_website`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`role`	No
`industry`	No
`location`	No
`is_active`	No
`is_shared`	No
`created_at`	No
`is_default`	No
`updated_at`	No
`company_name`	Yes
`company_size`	No
`hiring_context`	No
`active_jd_title`	No
`candidate_count`	No
`company_website`	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 / active_jd_title
```
Added value: +{
+  "$ref": "#/properties/industry"
+}
```
- addedOutput schema / properties / candidate_count
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / is_active / $ref
```
Removed value: -"#/properties/is_default"
```
- addedOutput schema / properties / is_active / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- addedOutput schema / properties / is_default / $ref
```
Added value: +"#/properties/is_active"
```
- removedOutput schema / properties / is_default / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```
- addedOutput schema / properties / is_shared
```
Added value: +{
+  "$ref": "#/properties/is_active"
+}
```
- addedOutput schema / properties / role
```
Added value: +{
+  "$ref": "#/properties/industry"
+}
```
First observedMar 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent). The description adds context beyond them by disclosing the 'Free' billing status and the workflow role, though it omits any warning about the non-idempotent nature (repeated calls create duplicate contexts).

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, front-loaded sentences with zero filler: what it creates, what it returns, how the id is used, and its position/cost. Every sentence earns its place.

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?

The workflow positioning, downstream id usage, and cost note make the tool's role clear, and the output schema covers the return value. However, for a create tool with a nested hiring_context object and an is_default flag, the description offers no guidance on the input parameters.

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

Parameters2/5

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

Schema description coverage is only 14%, so the description is expected to compensate, yet it explains none of the 7 parameters (company_name, industry, location, is_default, company_size enum, the nested hiring_context object, company_website). It only describes the return id, not the inputs.

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 new hiring context (company profile)') plus the purpose ('for organizing candidates and JDs'), which cleanly separates it from siblings like atlas_list_contexts and atlas_update_context.

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 positions it as 'the first step in the Atlas workflow' and names the downstream tools that consume the returned id (atlas_upload_candidate, atlas_create_jd, atlas_list_candidates, analysis/batch/utility tools), so the agent knows exactly when to call it first.

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?