Skip to main content
Glama

update_profile

Replace the stored profile facts. Call get_profile and get_schema with document profile in this turn. Pass that version and the profile fields. On profile_invalid, fix validation and retry with the same version. On profile_conflict, call get_profile again. version null creates the profile file. To keep the website off new resumes and cover letters, send preferences { siteLinkInDocuments: false }; leaving preferences out keeps the stored value, and sending preferences replaces all of them, so keep targetRoles and situation from get_profile. siteLink is read-only and is ignored here. This does not change the website or existing resumes and cover letters.

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": {
      "version": "<version>",
      "profile": "<profile>"
    },
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=false, openWorld=false; the description adds far more: full-replacement semantics, that omitting preferences preserves the stored value, that sending preferences wipes targetRoles/situation, and that siteLink is ignored as read-only. The "replace" wording is reconciled with destructiveHint=false by the documented omission-preserves rule, so this is disclosure rather than contradiction. Error-code behavior (profile_invalid, profile_conflict) is also specified.

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, then prerequisite, then error handling, then the preferences caveat — a logical call order with no filler sentences. It is dense to the point of being run-on (semicolon-chained preferences guidance), costing a little scanability, but nothing is redundant.

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 nested-object mutation with no output schema and no enum constraints, the definition still covers the concurrency model, both error branches, partial-update hazard, read-only fields, and side-effect boundaries. An agent has everything needed to call it correctly and to recover from failures without further tool calls.

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

Parameters5/5

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

Schema coverage is 0% and the profile object is a free-form nested object, so the description carries the full burden — and does: version is a concurrency token sourced from get_profile with null meaning create, and profile.preferences is spelled out field by field (siteLinkInDocuments, targetRoles, situation) with replace-vs-omit semantics. No other definition would tell an agent that siteLink is read-only and ignored.

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 ("Replace the stored profile facts") and immediately scopes it away from siblings: it explicitly says it does not change the website or existing resumes and cover letters, which are handled by update_resume/update_cover_letter. An agent can distinguish this from get_profile and the document-update tools without opening any 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?

Gives an explicit prerequisite sequence (call get_profile and get_schema with document profile in this turn, pass that version), plus named-alternative routing: on profile_invalid fix and retry with the same version, on profile_conflict call get_profile again. It also defines the creation path (version null) and the opt-out path for preferences, leaving nothing about when/how to use it to 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.

Resources