Skip to main content
Glama

set_name

Idempotent

Change your account's display name to identify yourself in Agent Uplink messaging.

Instructions

Changes my account's display name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesNew display name (max 64 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so safety and repeat-call behavior are covered. The description adds only the fact that the operation targets 'my account', without saying which account context applies, whether the change is reversible, or what a failed validation returns.

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?

One short, front-loaded sentence with no filler or redundancy. It is arguably too terse rather than bloated, which is a completeness issue rather than a structural one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with full schema coverage and informative annotations, the definition is minimally adequate. It still leaves the account-context question open ('my account' relative to a multi-account toolset that includes 'use_account' and 'list_accounts'), which matters for correct invocation.

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?

The single parameter has 100% schema coverage, including the 64-character maximum and non-empty constraint, so the schema carries the semantics. The description restates 'display name' but adds no format, uniqueness, or trimming details beyond the structured field.

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 ('Changes') and resource ('my account's display name'), so the agent knows exactly what is mutated. It does not differentiate from the sibling 'set_profile', which plausibly could also alter a display name, leaving a small ambiguity.

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?

No when-to-use guidance is offered: nothing states whether this targets the active account (versus one selected via 'use_account') or when to prefer 'set_profile' instead. The agent must infer usage entirely from the name.

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