Skip to main content
Glama
Foto MCP Server
by thesven

foto_list_profiles

Lists all saved Foto account profiles and identifies the currently active account so you can confirm which profile is in use.

Instructions

List all saved Foto account profiles (e.g. 'default', 'street', 'studio') and show which account is currently active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. The verb "list" and the example values ('default', 'street', 'studio') make the read-only nature evident without saying so explicitly, and the active-account marker is useful behavioral detail. It omits whether auth is required to call it, what happens with zero saved profiles, and whether the active marker is a field or a separate entry.

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?

One front-loaded sentence names the resource, seeds concrete example profile names, and states the active-account behavior. Nothing is repeated from structured fields and nothing is wasted.

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 zero-parameter read tool with no output schema and no annotations, the description conveys both what is listed and the extra active-account signal. The remaining gap is small: it doesn't say what the result looks like when no profiles are saved, which matters slightly more here because there is no output schema to fall back on.

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?

The tool takes zero parameters, so there is nothing the schema needs the description to explain; baseline 4 applies. The description correctly introduces no parameter-like concepts and instead spends its words on the return content.

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?

"List all saved Foto account profiles" gives a specific verb (list) and resource (saved account profiles), and the added clause about showing the active account pins down the payload. It is clear but does not name or contrast with the closest sibling (foto_auth_status), so an agent must infer the boundary itself.

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?

Use is implied — you'd call this to see which saved accounts exist and which is active — but there is no statement of when to prefer it over foto_auth_status, no prerequisite (must a profile exist first?), and no exclusion. Adequate, not instructive.

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