Skip to main content
Glama

Use headshot as profile photo

use_headshot_as_profile_photo
DestructiveIdempotent

Set one of the user's finished AI headshots as their Himalayas profile photo, by session id and image id from list_headshots. Uses the connected Himalayas account; no extra sign-in needed.

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": {
      "session_id": "<session_id>",
      "image_id": "<image_id>"
    },
    "name": "use_headshot_as_profile_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idYesImage id from list_headshots
session_idYesSession id from list_headshots

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is largely covered. The description adds useful auth context ('Uses the connected Himalayas account; no extra sign-in needed') but does not disclose what gets destroyed — namely whether the existing profile photo is overwritten or recoverable — which is the key behavioral question for a destructive write.

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?

A single well-formed sentence that front-loads the action and resource, then appends the sourcing and auth context. 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 simple two-parameter tool with no output schema and annotations covering safety, the description supplies the essential context: where the ids come from and that authentication is already handled. The only real omission is the fate of the pre-existing profile photo, which is a minor gap for a destructive operation.

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 description coverage is 100% and both parameters are self-documented as ids from list_headshots. The description reinforces that provenance but adds no format, type, or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb ('Set ... as their Himalayas profile photo') with a precise resource and scope, plus the identifying keys needed. An agent can distinguish it from siblings like list_headshots, get_headshots_link, and update_profile_photo without opening the schema.

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

Usage Guidelines4/5

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

The description establishes the prerequisite flow by stating the ids come 'from list_headshots' and that the headshot must be 'finished,' which tells the agent when this call is valid. It stops short of naming an explicit alternative (e.g., update_profile_photo for a non-headshot image) or stating when not to use it.

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.