Skip to main content
Glama

citadel_start_profile_upgrade

Start an A-to-Z Full Profile Upgrade session without requiring a prior user account. Stages 1-8 photos (via HTTPS URLs or base64 data URIs) or mints 6 signed upload slots + browser handoff URL, creates a $24.99 Full Profile Upgrade Stripe Checkout (30 credits: 15 Audit + 8 first Forge Photo + 7 left), and returns agent_session_token.

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

Input Schema

NameRequiredDescriptionDefault
emailNoOptional buyer email for Stripe checkout & report delivery
contextNoOptional dating context (app, city, goal, gender, age_bracket, residency, personal_facts)
image_urlsNoHTTPS URLs of 1-8 dating profile photos
image_base64NoBase64 or data:image/* URIs of 1-8 dating profile photos
agent_platformNoCaller platform name (e.g. chatgpt, gemini, grok, cursor, custom)
idempotency_keyNoOptional idempotency key for checkout creation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional dating context (app, city, goal, gender, age_bracket, residency)"New value: +"Optional dating context (app, city, goal, gender, age_bracket, residency, personal_facts)"
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover only readOnly/openWorld/idempotent/destructive hints, and the description adds materially important behavior on top: the tool creates a real $24.99 Stripe Checkout, allocates credits (15 Audit + 8 Forge Photo + 7 remaining), mints 6 signed upload slots plus a browser handoff URL, and returns an agent_session_token. The monetary charge and the dual photo-ingestion modes are exactly the kind of side-effect disclosure an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence with the core purpose front-loaded and no filler; every clause conveys a distinct fact (accountless start, photo modes, checkout price, credit split, token). It is a run-on that crams four ideas together, slightly hurting scannability.

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?

With 6 parameters, a nested context object, and no output schema, the description does the important work of naming the returned agent_session_token and the checkout/credit outcomes. It stops short of saying what the caller should do next (e.g., poll citadel_get_session_status) or how the browser handoff should be surfaced to the user.

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 coverage is 100%, so each parameter is already documented, and the description largely restates it (1-8 photos via HTTPS URLs or base64). It does add the 'or' relationship implying image_urls vs image_base64 are alternative ingestion modes, but leaves idempotency_key and agent_platform unexplained beyond the schema.

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+resource ('Start an A-to-Z Full Profile Upgrade session') and a distinguishing scope qualifier ('without requiring a prior user account'). It enumerates the concrete artifacts produced — staged photos or signed upload slots, a Stripe Checkout, and an agent_session_token — which clearly separates it from siblings like citadel_evaluate_profile_readiness and citadel_forge_profile_photo.

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?

The 'without requiring a prior user account' clause implies this is the accountless entry point into the full upgrade pipeline, which is useful routing context. However, it never states when NOT to use it (e.g., when an account/session already exists) or names a specific alternative sibling for partial flows such as single-photo forge or readiness check.

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.