set_avatar
Upload an image URL to set it as your profile avatar in a single step.
Instructions
Upload image and set as profile avatar in one step.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| image_url | Yes | Image URL to upload and set as avatar |
Upload an image URL to set it as your profile avatar in a single step.
Upload image and set as profile avatar in one step.
| Name | Required | Description | Default |
|---|---|---|---|
| image_url | Yes | Image URL to upload and set as avatar |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must fully convey behavioral traits. It only states the action (upload and set avatar) but does not disclose whether it replaces the current avatar, size limits, reversibility, authentication requirements, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently conveys the core action without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with one parameter and no output schema, the description covers the basic action but lacks context about side effects, prerequisites, or constraints like user authentication or avatar slot availability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter. The description adds no new meaning beyond the schema's 'Image URL to upload and set as avatar'. With high coverage, baseline is 3, and no extra context is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it uploads an image and sets it as profile avatar in one step, distinguishing it from sibling tools like upload_image_from_url (upload only) and update_my_profile (profile update without upload).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as upload_image_from_url, update_my_profile, or other profile-related tools. The description does not specify prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Launch-On-Basis/MCP-TS'
If you have feedback or need assistance with the MCP directory API, please join our Discord server