Skip to main content
Glama

A person's account

my_account
DestructiveIdempotent

Needs the person's access token. action: profile (read), update (name, language, market, watch e-mails), sign_out, delete (permanent, needs confirm).

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": {
      "action": "<action>"
    },
    "name": "my_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name
scopeNoglobal or local (sign_out)
actionYesOperation to run; help {topic:"my_account"} lists each one's arguments
localeNoLanguage of e-mails
confirmNoThe account e-mail (delete)
countryNoMarket country
watch_emailsNoReceive watch e-mails

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"my_account\"} lists each one's arguments"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description pinpoints which action is destructive (delete, permanent) and what it requires (confirm). It also discloses the auth requirement, which annotations do not cover. It stops short of describing effects on sign_out scope or update side effects, keeping it at a 4 rather than 5.

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?

Extremely compact with zero filler and the hard prerequisite front-loaded. The parenthetical field list is somewhat telegraphic ('market', 'watch e-mails') but readable for an agent; nothing is wasted.

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 7-parameter, 4-action destructive tool with no output schema, the description covers auth, action inventory, destructive semantics, and confirmation. The remaining gap is minor: it does not point to the 'help' topic for per-action argument details, despite the enum description doing so.

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, but the description adds a cross-cutting mapping the schema lacks: which parameters belong to the update action (name, language, market, watch e-mails) and that confirm pairs with delete. This action-to-parameter linkage is genuinely useful beyond the per-field descriptions.

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 names the resource (the person's account) and enumerates the four concrete actions: profile read, update of specific fields, sign_out, and permanent delete. An agent can tell what the tool does at a glance, though it relies on the sibling list rather than explicit wording to establish that this is the account-management tool in the family.

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?

It states a prerequisite (an access token is required) and flags that delete is permanent and needs confirmation, which is real usage guidance. It does not, however, say when to pick this over an alternative such as the 'help' sibling for discovering per-action arguments, leaving selection context largely implied.

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