Skip to main content
Glama

citadel_forge_profile_photo

Quote or generate an identity-locked Profile Forge photo (8 credits/photo). action='quote' previews exact credit cost without charging; action='generate' requires explicit human confirmation (confirm_quote=true) and auto-provisions a $14.99 (15 credits) Stripe top-up checkout if remaining credits < 8.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_session_token": "<agent_session_token>"
    },
    "name": "citadel_forge_profile_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo'quote' (default), 'generate' (requires confirm_quote=true), or 'poll'
job_idNoOptional Forge job_id when polling
roast_idNoOptional roast_id if not carried inside session token
confirm_quoteNoMust be true after the human explicitly confirms the 8-credit Forge quote
idempotency_keyNoOptional idempotency key
agent_session_tokenYesSession token from start/audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: 8 credits per photo, an automatic $14.99/15-credit Stripe top-up when balance is below 8, and a mandatory human-confirmation gate on generate. These are the side effects and spend conditions an agent must know before calling a non-readOnly, non-idempotent tool.

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?

Two sentences, front-loaded with purpose and price, then the mode semantics and the payment fallback. No filler; every clause carries decision-relevant information.

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 mutation tool with a real financial side effect and no output schema, the description covers cost, confirmation, and top-up adequately. It omits what generate returns (presumably a job_id) and how polling is used, a modest gap for the multi-step flow.

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?

Schema coverage is 100%, so baseline would be 3; the description earns above that by explaining the inter-parameter dependency (generate requires confirm_quote=true) and the meaning of quote versus generate. It says nothing about job_id or idempotency_key semantics, which the schema covers only thinly.

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 pair (quote/generate) and resource (identity-locked Profile Forge photo) with the per-unit price. It cleanly separates its own two modes, but never positions itself against siblings like citadel_start_profile_upgrade, so an agent gets no explicit differentiation.

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

Usage Guidelines4/5

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

Gives concrete when-to-use context: quote previews cost without charging, generate requires explicit human confirmation. The 'poll' action that appears in the enum is not covered by the description, leaving one mode's usage unstated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.