Skip to main content
Glama

Set resume style

set_resume_style
Idempotent

Change a resume's visual style: accent colour, layout, and/or font. Fields left out are preserved. accent_color: navy, emerald, burgundy, charcoal, violet (there is no pure red or blue). layout: classic, sidebar, header_banner, editorial, timeline, compact. font: default (Inter, sans-serif), classic (Lora, serif), modern (Jost, sans-serif). Applies instantly and returns the resulting style. Style is not part of resume versions: history and restore leave it as is. Returns 'not_found' if the resume does not exist or does not belong to the current user, and 'invalid_payload' if no field is provided or a value is not one of the allowed options.

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": {
      "input": "<input>"
    },
    "name": "set_resume_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
fontYesResulting font pair: default = Inter, classic = Lora, modern = Jost.
layoutYesResulting layout.
resume_idYesId of the restyled resume.
accent_colorYesResulting accent colour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / font / description
      Previous value: -"Resulting font pair."New value: +"Resulting font pair: default = Inter, classic = Lora, modern = Jost."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that changes apply instantly, the resulting style is returned, style is excluded from version history/restore, and specific error outcomes occur for missing resumes or invalid payloads. This gives the agent strong operational context for a non-destructive mutable tool.

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?

The description is front-loaded and dense with relevant information, with no wasted sentences. It is somewhat long due to exhaustive enum lists, but those lists directly support correct invocation.

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?

For a non-destructive, idempotent style mutation with an output schema, the description covers allowed values, partial-update semantics, instant application, versioning behavior, and failure modes. An agent has enough information to call it correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description spells out accepted values for accent_color, layout, and font, including font family mappings, and reinforces that omitted fields retain their current values. It also adds useful mapping guidance for free-text colour requests, though much of this overlaps with the schema's property descriptions.

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?

The description gives a specific verb and resource: change a resume's visual style, including accent colour, layout, and font. It clearly distinguishes styling from content-editing siblings such as update_resume_section or rename_resume.

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?

It clearly frames the tool around visual styling and explains that omitted fields are preserved, so the agent knows partial updates are allowed. It does not explicitly name an alternative for non-style resume edits, but the context is sufficiently clear without requiring sibling inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.