Skip to main content
Glama
Foto MCP Server
by thesven

foto_switch_profile

Activate a saved Foto account profile to switch between personal, street photography, and studio accounts. Use it to change the active publishing identity before uploading images.

Instructions

Switch the active Foto account profile on the fly (e.g. between personal, street photography, and commercial studio accounts).

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": {
      "profileName": "<profileName>"
    },
    "name": "foto_switch_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNameYesThe name of the saved profile to activate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure for a state-changing operation. Beyond the vague 'on the fly' hint, it says nothing about auth requirements, whether the switch is reversible, what happens to an unknown profileName, or whether it affects subsequent tool calls on the session.

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 short sentence with the action front-loaded and the examples parenthetically contained. Nothing is wasted and no reader has to parse past filler.

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, no-output-schema tool this is close to adequate, but the absence of annotations means the definition should carry more of the behavioral contract. An agent still cannot tell whether the switch succeeds silently, errors on an unknown name, or invalidates an authenticated session.

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% for the single required parameter, so the baseline is 3. The parenthetical examples of profile kinds (personal, street photography, commercial studio) add a little meaning about what a profile represents, but they are illustrative rather than actionable formatting guidance.

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?

The description gives a specific verb+resource pair ('switch the active Foto account profile'), which is clearly distinct from sibling readers and editors such as foto_get_user_profile or foto_update_user_profile. The only gap is that it does not name any sibling to differentiate against explicitly.

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?

'On the fly' implies this is a runtime session switch rather than an edit of saved profile data, which is useful context. However, there is no explicit when-to-use versus when-not guidance, no mention of prerequisites, and no statement about what to do if the requested profile is not among the saved ones.

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