CareerProof MCP

atlas_get_analytics

Read-onlyIdempotent

Get comprehensive talent analytics dashboard data for a hiring context (candidate stats, analysis coverage, fit score distributions). Requires context_id from atlas_create_context or atlas_list_contexts. Read-only summary, no downstream chaining needed. Free.

Input Schema

Name	Required	Description	Default
`context_id`	Yes	Context ID from atlas_create_context or atlas_list_contexts

Output Schema

Name	Required	Description	Default
`analyzed_count`	No
`avg_gem_scores`	No
`top_candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 5, 2026

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

removedOutput schema / properties / analysis_coverage

Removed value: -{
-  "$ref": "#/properties/fit_score_distribution"
-}

removedOutput schema / properties / analyzed_count / $ref
```
Removed value: -"#/properties/total_candidates"
```
addedOutput schema / properties / analyzed_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / average_gem_score

Removed value: -{
-  "$ref": "#/properties/total_candidates"
-}

addedOutput schema / properties / avg_gem_scores

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

removedOutput schema / properties / fit_score_distribution

Removed value: -{
-  "anyOf": [
-    {},
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / pending_count

Removed value: -{
-  "$ref": "#/properties/total_candidates"
-}

removedOutput schema / properties / top_candidates / $ref
```
Removed value: -"#/properties/fit_score_distribution"
```

addedOutput schema / properties / top_candidates / anyOf

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

removedOutput schema / properties / total_candidates

Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}

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 readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds genuinely new context beyond that: the 'no downstream chaining needed' workflow note and the 'Free' cost signal, neither of which is expressed in the structured fields.

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 tight sentences with the core purpose front-loaded, followed by prerequisite and then the read-only/cost notes. The one-word 'Free.' sentence is compact and carries distinct information, so nothing is wasted.

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 annotations carry the safety profile, so the description only needs to cover purpose, prerequisite and cost — all of which it does. The one residual gap is the absence of a routing rule against sibling analytics tools.

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% and the single context_id parameter is already documented in the schema. The description repeats the same source hint ('from atlas_create_context or atlas_list_contexts') without adding format or validation detail, so it does not exceed the schema's own documentation.

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 and resource ('Get comprehensive talent analytics dashboard data') and enumerates the content (candidate stats, analysis coverage, fit score distributions). It does not explicitly distinguish itself from near-neighbors such as atlas_get_analysis or atlas_list_analyses, so the agent must infer the difference from the word 'dashboard'/'comprehensive'.

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?

Gives a clear prerequisite (context_id from atlas_create_context or atlas_list_contexts) and states the operation is terminal ('no downstream chaining needed'). It offers no explicit when-not or named alternative, so an agent choosing between this and atlas_get_analysis gets context but no routing rule.

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?