CareerGenius

Render resume Word file

careergenius_render_resume_docx

Read-onlyIdempotent

The same resume layout as an editable Word (.docx) file, for a person who wants to change it before sending. Returns the file as an embedded resource (base64); nothing is stored. No AI. Counts one call of the monthly allowance. Without a key: one of the conversation's 10 free keyword/PDF calls.

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": {
      "on_behalf_of": "<on_behalf_of>",
      "resume": "<resume>"
    },
    "name": "careergenius_render_resume_docx"
  }
}

Input Schema

Name	Required	Description
`resume`	Yes	The resume content, exactly as it should appear. Nothing is added, reworded or checked: this tool only lays it out. At most 45,000 characters of JSON.
`template`	No	classic (serif, centred header) or modern (sans-serif, left-aligned). Default classic.
`page_size`	No	Default letter.
`on_behalf_of`	Yes	Required. You confirm a person asked for this, and the resume is theirs (or they are authorised to use it).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the return transport (embedded resource, base64), the stateless nature ('nothing is stored'), that no AI processing occurs, and the cost model including free-tier behavior. These are exactly the operational facts an agent needs before invoking an allowance-consuming tool.

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?

Five short clauses, output format and statelessness front-loaded before the quota notes, with zero filler. Every sentence contributes a fact the agent would otherwise lack.

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?

Despite a deeply nested schema and no output schema, the description covers the return value shape, cost, and statelessness, while the schema fully documents the large resume payload. Nothing an agent needs to call this correctly is missing.

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%, including the nested resume object, template/page_size enums, and the on_behalf_of attestation, so the schema carries the parameter burden. The description adds no parameter-level detail beyond what is already structured, making baseline 3 appropriate.

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 deliverable (an editable .docx Word file) built from 'the same resume layout', which implicitly but unmistakably distinguishes it from the sibling PDF renderer. An agent can tell whether it is producing an editable Word file or a fixed PDF without opening either 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?

Names the selecting condition precisely: 'for a person who wants to change it before sending', which routes against render_resume_pdf. It doesn't explicitly name that sibling or state the inverse case, but the usage context is clear and unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CareerGenius 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?