CareerProof MCP

atlas_update_context

Idempotent

Update a hiring context's details (name, industry, size, hiring context). Requires context_id from atlas_create_context or atlas_list_contexts. Returns the updated context object. Free.

Input Schema

Name	Required	Description
`industry`	No
`location`	No
`is_active`	No
`context_id`	Yes	Context ID from atlas_create_context or atlas_list_contexts
`is_default`	No
`company_name`	No
`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.

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

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile (mutation, idempotent, non-destructive, non-open-world). The description adds two useful facts not in annotations: it returns the updated object and it is 'Free'. But it omits partial-update semantics (whether omitted fields are preserved) and any auth requirements, so it adds only moderate value over the structured data.

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 tight sentences, front-loaded with the action, no filler. Every sentence contributes (purpose, prerequisite, return value/cost). Slightly clipped on detail but structurally sound.

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 values need not be described, and annotations cover the safety profile, which lowers the bar. Still, for a 9-parameter mutation tool with a nested object and 11% schema coverage, the description omits update semantics and most field meanings, leaving an agent under-informed.

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 11% across 9 parameters including a nested object, so the description carries the burden but names only 4 fields loosely (name, industry, size, hiring context). The enum values for company_size, booleans (is_active, is_default), location, company_website, and the nested hiring_context sub-shape are left undocumented.

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?

Specific verb+resource: 'Update a hiring context's details' with an enumerated field list (name, industry, size, hiring context). It distinguishes itself from sibling read/create tools by referencing atlas_create_context and atlas_list_contexts as ID sources. Lacks explicit contrast with other update_* siblings, but the resource is unambiguous.

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?

States a prerequisite ('Requires context_id from atlas_create_context or atlas_list_contexts'), which is genuine usage guidance. However, it gives no when-to-use vs alternatives, no exclusions, and no indication of when an agent should update versus recreate a context.

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?