Skip to main content
Glama
Sign In
Foto MCP Server

Foto MCP Server

by thesven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

foto_logout

Logs out of the Foto app and deletes stored credentials from local disk to end the session and remove local access.

Instructions

Log out of Foto app and delete stored credentials from local disk.

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_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral burden; it does disclose the destructive local side effect of deleting stored credentials, which is the key trait. However, it is silent on whether the server-side session/token is revoked, whether the local deletion happens if the server call fails, and whether the operation is safe to repeat.

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 well-formed sentence with no filler, front-loading the primary action and appending the consequential side effect.

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 no-parameter, no-output-schema tool this is nearly complete: what it does and what it destroys are both stated. Only edge-case behavior (already logged out, failure handling, server-side session state) is left unaddressed.

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 for the description to clarify beyond the action itself; baseline applies.

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 ('Log out of Foto app') plus the concrete side effect ('delete stored credentials from local disk'), which distinguishes it cleanly from siblings like foto_login and foto_auth_status.

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 name and by its obvious role as the counterpart to foto_login, but the description never states when to log out, whether an active session is required, or points to foto_auth_status for checking state first.

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

Deploy Server

Other Tools