Skip to main content
Glama

set_profile

Idempotent

Updates your account's profile description (up to 500 characters) so other sessions, admins, and viewers can identify you; send an empty string to remove it.

Instructions

Changes my account's profile description (up to 500 characters; an empty string removes it). Visible to other sessions, the admin app, and the viewer.

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

Input Schema

NameRequiredDescriptionDefault
descriptionYesRole description

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

A3.8/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent, non-destructive, and closed-world. The description adds real context beyond that: the 500-character limit, that an empty string clears the value, and the visibility surface (other sessions, admin app, viewer). It doesn't say whether the change is confirmed or returned, but the key behavioral facts are covered.

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?

One sentence, front-loaded with the verb and resource, with the limit and clearing semantics packed into a parenthetical and the visibility note trailing. No filler or repetition.

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 one-parameter, non-destructive mutation with annotations and no output schema, the description supplies everything needed to invoke it correctly: what it changes, limits, clearing behavior, and who sees the result. Only a note on confirmation/return behavior is missing, which is minor here.

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 100% and maxLength 500 is already in the schema, so restating the limit adds little. The one genuine addition is that an empty string removes the description, which the schema does not express; with a single documented parameter, baseline 3 is appropriate.

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?

States a specific verb and resource with explicit scope: 'Changes my account's profile description'. The scope ('my account', as opposed to a server or channel) distinguishes it from sibling mutators like set_name, which the description doesn't name but doesn't need to.

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?

Usage is implied by the single operation plus the note that an empty string removes the description, which is a useful edge-case cue. There is no explicit statement of when to use this versus set_name or other profile-related calls, so guidance is adequate but not routing.

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