Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Update Me

updateMe
Destructive

Update your account profile details, including name, avatar, account card, or password, through the Cloady API to keep your account information current.

Instructions

Update your name, avatar, account card or password (requires full scope).

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": "updateMe"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=true, and openWorld=true, so the safety profile is covered. The description adds meaningful behavioral context by naming the required full scope and clarifying which self-account fields are mutated, though it does not itself explain irreversibility or the effect of null values on password or payment method.

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?

The description is a single, front-loaded sentence that lists the mutable fields and appends the scope requirement without filler. Every phrase contributes to identifying what the tool changes.

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 destructive self-update tool with a nested request body and no output schema, the description covers the mutable fields and the scope prerequisite, while annotations carry the safety profile and the schema documents parameter details. A small gap remains around the side effects of clearing password or payment method, but that is partly covered by schema property descriptions.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds semantic mapping beyond the schema by translating 'avatar' to the image field and 'account card' to paymentMethodId, and it notes that password changes require full scope, which is useful context not present in the schema property names alone.

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 states a specific verb, 'Update', and enumerates the concrete resources affected: name, avatar, account card, and password. It is clear that the tool modifies the authenticated user's own profile, but it does not explicitly differentiate itself from siblings such as getMe or startCardSetup.

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

Usage Guidelines3/5

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

The only explicit usage condition is 'requires full scope', which is a useful prerequisite. However, the description does not say when to use this tool versus alternatives like getMe, startCardSetup, or updateNotificationPreferences, so usage is mostly implied by the verb and field list.

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

Deploy Server

Other Tools