CareerProof MCP

atlas_create_context

Create a hiring context (a company or role) that holds candidates and JDs. Returns its id, the context_id the other atlas_* tools take. Reuse one from atlas_list_contexts if it exists. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>"
    },
    "name": "atlas_create_context"
  }
}

Input Schema

Name	Required	Description	Default
`industry`	No
`location`	No
`is_default`	No
`company_name`	Yes
`company_size`	No
`hiring_context`	No
`company_website`	No

Output 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.

Changed1 schema field changedNov 11, 2026
- removedInput schema / properties / hiring_context / description
```
Removed value: -"Hiring context details (open roles, budget, goals)"
```
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/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write. The description adds context the annotations cannot: the resource is a container for candidates and JDs, the call returns the 'context_id' that other atlas_* tools consume, and it is 'Free' – a cost disclosure that materially affects agent behavior. It does not say what happens on a duplicate company_name, which is the main remaining behavioral unknown.

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?

Three short sentences, each doing distinct work: what it creates, what it returns and why that matters, and when to avoid it. Front-loaded with the action and zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-shape explanation is rightly omitted, and the description covers the container semantics and the context_id handoff well. But for a 7-parameter tool with a nested object and no schema descriptions anywhere, the definition is incomplete – an agent must open the schema blind to tell whether is_default or hiring_context fields matter.

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 0% across 7 parameters, including a nested hiring_context object with seven sub-fields, so the description carries the full burden here. It mentions no parameter at all – not the required company_name, not the enum-constrained company_size, not is_default or the nested hiring_context. Only the baseline signal of 'free' survives as useful new meaning.

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 hiring context') and defines the resource in plain terms ('a company or role that holds candidates and JDs'), which no sibling name conveys on its own. It also names the sibling to check first (atlas_list_contexts), so an agent can route without opening another schema.

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?

'Reuse one from atlas_list_contexts if it exists' is an explicit when-not-to-use rule with the alternative named. It stops short of covering adjacent cases (e.g. when to prefer atlas_update_context on an existing context, or what is_default implies), so it is strong but not exhaustive.

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?