Skip to main content
Glama

Update my profile

update_my_profile
Idempotent

Update the client's name, phone, or language with all their guides. Email cannot change.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_my_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNo
localeNoLike en_US or fi_FI.
last_nameNo
first_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world), so the description's contribution is the side effect that changes propagate "with all their guides" and that email is immutable. Those are real behavioral facts beyond the annotations, but partial-update semantics for the four optional fields go unmentioned.

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?

Two tight sentences, front-loaded with the mutable fields and ending with the key constraint. The phrase "with all their guides" is slightly cryptic about what exactly is being shared, costing it the top score.

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 four-parameter, zero-required mutation with no output schema, the description covers the fields, the broadcast effect, and the immutability constraint, which is close to sufficient. What is missing is the partial-update contract (unspecified fields stay unchanged) and any hint of what the call returns.

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 only 25% (just locale), so the description's mapping of "name, phone, or language" onto first_name/last_name/phone/locale is genuinely useful. It does not clarify that all four are optional and only supplied fields change, and the "email cannot change" note references a field that does not exist in the schema, which could mislead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("Update") and enumerates the mutable resource fields (name, phone, language) on the client's own profile, which cleanly separates it from get_my_profile. It stops short of naming the read sibling explicitly, but the mutation framing is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus get_my_profile or any other sibling, and no prerequisites. The only guidance-like content is the exclusion "Email cannot change," which constrains a field rather than telling the agent when this tool is the right choice.

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