Skip to main content
Glama
Sign In
Identity Forge MCP

Identity Forge MCP

Official
by KasayoDotCom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List image directions

list_image_directions

Browse image direction options for a selected design kit, helping you avoid generic stock imagery. Returns summaries of each direction's treatment, process, and subject matter.

Instructions

Browse image directions, which decide how a project's photography and illustration should be made: the process, treatment, and subject matter. Use one when a kit is chosen but the imagery still has no direction, which is where most agent-built pages fall back to stock-looking filler. Returns judgment summaries with no export payload, so pick a slug and call get_image_direction for the implementable version. A direction sits alongside the design kit and never replaces it; the kit still owns color, type, and brand rules. Read-only and free, and Pro records appear in the list without exposing their contents.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch names, aliases, visual signals, fit, and agent tags.
useNoThe website job the image must perform.
sortNoCurated order, alphabetical order, or Free records first.
tierNoShow Free records, Pro records, or both.
familyNoOne or more image-process families.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/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 so excellently: 'Returns judgment summaries with no export payload', 'Read-only and free', and 'Pro records appear in the list without exposing their contents.' These are key behavioral disclosures beyond the schema.

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 description is composed of five focused sentences, each adding distinct value: purpose, when to use, return behavior, relationship to design kit, and access limitations. There is no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with 5 optional parameters and no output schema, the description sufficiently covers the purpose, usage context, return behavior (summaries), pointer to the detailed sibling tool, and read-only/free status. It is a complete description for an agent to decide when and how to invoke it.

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%—every parameter has a clear description in the schema. The tool description does not add additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Browse image directions' and explains what image directions are (process, treatment, subject matter for photography/illustration). It also distinguishes itself from the sibling get_image_direction by specifying that it returns judgment summaries rather than the implementable version.

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

Usage Guidelines5/5

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

The description gives explicit usage context: 'Use one when a kit is chosen but the imagery still has no direction...' and directs to the alternative tool: 'pick a slug and call get_image_direction for the implementable version.' This clearly states when to use this tool vs. the sibling.

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