Skip to main content
Glama

Set my primary resume

setPrimaryResume
Idempotent

Make one of the candidate's resumes the primary one, the version Clera sends with every introduction from now on. Take the resumeId from listResumes; another candidate's id is refused.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "resumeId": "<resumeId>"
    },
    "name": "setPrimaryResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYesThe resumeId from listResumes.

Output Schema

NameRequiredDescriptionDefault
nameYes
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description goes further by disclosing the lasting effect on future introductions and the cross-candidate ownership refusal. It also adds a data-handling disclosure that inputs and results are recorded for tracking and support, which is real behavioral context not present 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.

Conciseness4/5

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

The core behavior and the ID sourcing rule are front-loaded in the first sentence, with the ownership constraint close behind. The trailing data-recording sentence is boilerplate but short enough not to obscure the substance.

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?

For a single-parameter mutation with an output schema available, the definition covers what changes, where the ID comes from, and what is rejected. Nothing essential to correct invocation is missing, though it is silent on what the response confirms or what happens to the previously primary resume.

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 coverage is 100% and the single parameter already carries a description plus UUID format and pattern, so the schema does the heavy lifting. The description restates the listResumes source and adds only the ownership rejection rule, which is a marginal gain over the schema.

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 (make primary) and resource (one of the candidate's resumes), plus the concrete consequence: it is "the version Clera sends with every introduction from now on." That downstream effect clearly separates it from sibling resume tools like deleteResume or editResumeDraft without needing their schemas.

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 workflow by naming listResumes as the source of the resumeId, and adds an exclusion rule that another candidate's id is refused. It does not spell out when-not-to-use conditions (e.g., versus tailoring or version management), but the calling context is unambiguous.

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.

Resources