CareerProof MCP

atlas_get_upload_link

Get a 30-minute link to a page (no sign-in) where the user drags in many CVs (PDF, DOCX, DOC, TXT) at once: the fastest way to add CVs, for more than one CV or any file. Give the user the link; when they say they are done, call atlas_list_candidates. 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": {
      "context_id": "<context_id>"
    },
    "name": "atlas_get_upload_link"
  }
}

Input Schema

Name	Required	Description	Default
`max_files`	No	Default 50
`context_id`	Yes	From atlas_list_contexts

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 11, 2026

changedInput schema / properties / context_id / description

Previous value: -"Hiring context ID from atlas_create_context or atlas_list_contexts"New value: +"From atlas_list_contexts"

changedInput schema / properties / max_files / description

Previous value: -"Most files the link accepts (default 50, max 100)"New value: +"Default 50"

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description carries the rest and delivers: 30-minute link expiry, no sign-in required, the interaction model (user drags files into a hosted page rather than passing data through the call), accepted formats (PDF, DOCX, DOC, TXT), and the cost ('Free'). These are operational facts the agent cannot get from 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.

Conciseness4/5

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

Front-loaded with the core action and the link's lifetime, then the follow-up instruction and cost as closers. Dense but nearly every clause carries information; the parenthetical format list and the colon-chained phrasing make it slightly run-on.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description covers what is returned (a link), its lifetime, that it requires no auth, what the user does with it, and the next tool to call. For a two-parameter link-generator this is complete enough to invoke correctly.

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 both parameters are documented inline, so the baseline is 3. The description adds only an implicit hint that many files are supported (relevant to max_files) but does not clarify the 50-default cap or how context_id from atlas_list_contexts is used.

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 ('Get a 30-minute link to a page ... where the user drags in many CVs') and scopes it to batch uploads ('for more than one CV or any file'), which distinguishes it from the single-CV sibling atlas_upload_candidate. An agent can identify the correct tool without opening a schema.

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 this as 'the fastest way to add CVs' for multi-file cases and prescribes the full workflow: hand the link to the user, then call atlas_list_candidates once they report being done. This names the follow-up sibling and the trigger condition, leaving nothing to inference.

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?