Skip to main content
Glama

Team: change my About-me image

team_about_image_set

Sets or removes the separate image shown beside your About me text on your Our Team page; independent from your profile photo. Give an https image_url or a small image_base64; PNG, JPEG or WebP. Without one the shared default image stays. Call without confirm first for a preview.

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

Input Schema

NameRequiredDescriptionDefault
clearNoRemove the current image instead of uploading (the page falls back to its default).
confirmNoSet true only on the second call, after the user approved the preview.
image_urlNohttps URL of a PNG, JPEG or WebP image (max 5 MB, 120-6000 px). Fetched by the server.
image_base64NoSmall image as base64 (about 180 KB at most); use image_url for anything larger.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, idempotent=false, but the description adds the genuinely non-obvious behavior: a preview-then-confirm workflow, the fallback-to-default when no image is given, and that the image is fetched from an https URL rather than uploaded inline. It does not cover what the preview actually shows or what happens to the previous image on replace — the latter matters given destructiveHint=false but clearing does remove content.

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?

Four short, dense sentences with the core purpose front-loaded and no filler. The preview instruction sits last rather than next to the confirm parameter, which slightly buries the most operationally important sentence.

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 5-param mutation tool with no output schema, the definition covers source options, format constraints, default fallback, and the confirm gate. The one gap is that 'preview' is never described — the agent must infer from the schema's preview_token that the first call returns a token.

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 coverage is 100%, so a 3 is the floor; the description goes beyond it by stating the either/or relationship between image_url and image_base64 ('Give an https image_url or a small image_base64'), which the schema lists only as separate optional properties. It also restates the no-image default behavior tied to those params.

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 and resource: sets or removes the About-me image on the Our Team page. The clause 'independent from your profile photo' cleanly separates it from the avatar/profile tools in the sibling list, so an agent can pick the right one without opening schemas.

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?

'Call without confirm first for a preview' gives an explicit two-step invocation protocol, and 'Without one the shared default image stays' tells the agent what happens when no source arg is supplied. What's missing is an explicit exclusion, e.g. pointing at the profile-photo tool for the avatar case, though the 'independent from your profile photo' framing implies 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.

Resources