Skip to main content
Glama
Foto MCP Server
by thesven

foto_upload_profile_photo

Upload a local image as your photographer profile avatar; it resizes to 400x400, normalizes sRGB color, and strips GPS before saving.

Instructions

Upload and set your photographer profile avatar photo from a local image file. Resizes to 400x400 square, normalizes sRGB color, strips GPS, uploads to Storage, and updates user-profiles.

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

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute local path to the image file to use as avatar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real side effects: resizing to 400x400, sRGB normalization, GPS stripping, Storage upload, and a user-profiles update. It omits auth requirements, whether an existing avatar is replaced, and what happens on an unsupported or missing file, so the mutation profile is only partially covered.

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?

A single dense sentence with the action front-loaded and the processing pipeline enumerated after it; every clause carries information. It is slightly list-like in the tail but wastes no words.

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 tool with no annotations and no output schema, the description covers the transformation pipeline well but leaves the agent guessing about authentication, overwrite semantics, and failure modes, which matter for a write 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 coverage is 100% and the single parameter is fully documented as an absolute local path. The description's 'local image file' phrasing reinforces the constraint but adds no format list, size limits, or path syntax beyond the schema.

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 pair ('upload and set') plus the exact resource ('photographer profile avatar photo') and the input source ('local image file'). An agent can distinguish this from foto_update_user_profile or foto_inspect_image without opening any schema.

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 phrasing 'your photographer profile avatar photo', which tells the agent this is the avatar-setting path, but there is no explicit when-to-use vs when-not guidance and no mention of prerequisites such as being logged in.

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