Skip to main content
Glama
Sign In
Foto MCP Server

Foto MCP Server

by thesven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

foto_get_user_profile

Fetches the authenticated Foto user's profile details and stats—username, bio, post count, following and followers—so AI assistants can personalize interactions and verify account context.

Instructions

Retrieve profile details and stats for the authenticated Foto user (username, bio, post count, following/followers).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a safe read operation and indicates the authentication context, but it does not describe error behavior when unauthenticated, rate limits, or whether the returned stats are live or cached. For a simple zero-parameter read tool, this is adequate but incomplete.

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?

The definition is a single front-loaded sentence with no filler. Every phrase contributes to specifying the resource, scope, or returned data.

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 simple zero-parameter read tool with no output schema, the description is nearly complete because it lists the main returned fields and states the authentication scope. It could be improved by mentioning what happens if the user is not authenticated, but the core contract is clear.

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 has zero parameters, so there are no parameter semantics to document beyond the empty schema. The description lists the returned fields, which adds useful meaning even though it is not a parameter concern.

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 uses a specific verb ('Retrieve') and resource ('profile details and stats') and scopes it to 'the authenticated Foto user'. It also enumerates the fields returned, which makes the tool's purpose clear. It does not explicitly differentiate itself from sibling tools such as foto_auth_status, but the resource and scope are distinct enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives like foto_auth_status or foto_login. The phrase 'authenticated Foto user' implies an authentication prerequisite, but the description does not state when this tool should or should not be called.

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