Skip to main content
Glama
Sign In
PhotoForge MCP Server

PhotoForge MCP Server

by TraGGERy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_identities

Retrieve digital twins and facial identity profiles so AI agents can select the correct identity for generating photos and videos.

Instructions

List user digital twins and facial identity profiles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/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 not state that this is a safe read-only listing, whether results are scoped to the authenticated user or workspace, or how many identities are typically returned. It only conveys the resource type, leaving the mutation/safety profile implicit.

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 front-loaded sentence that defines the resource with zero filler. Nothing is padded and the key noun is explained immediately.

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 zero-parameter list tool with no output schema, the description is minimally sufficient but leaves open what each identity record contains (id, name, thumbnails) and whether the list is paginated or complete, which an agent would want before chaining into create_identity or delete_identity.

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 the baseline is 4; there is nothing for the description to disambiguate in the schema.

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?

States a specific verb+resource and defines what an 'identity' is (digital twin and facial identity profile), which is genuinely clarifying given the ambiguous noun. It does not explicitly contrast with list_photo_packs or the create/delete_identity siblings, so it stops short of a 5.

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 guidance on when to call this versus siblings such as list_photo_packs or list_generations, and no note on whether it is a prerequisite for create_identity/delete_identity workflows. Usage is only inferable from the name.

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