Skip to main content
Glama

citadel_run_or_poll_profile_audit

Verify Stripe payment and run or poll the 15-credit Profile Signal Audit. Returns awaiting_payment (with checkout_url, 0 credits charged) until paid, processing (with job_id), or complete structured audit findings + report_url.

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

Input Schema

NameRequiredDescriptionDefault
roast_idNoOptional completed roast_id
image_urlsNoOptional additional HTTPS photo URLs if not passed in start
image_base64NoOptional additional base64 photos if not passed in start
idempotency_keyNoOptional idempotency key
agent_session_tokenYesToken returned by citadel_start_profile_upgrade

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, open-world operation but say nothing about cost. The description adds the critical behavioral facts: 15 credits charged, 0 credits charged while awaiting_payment, and a checkout_url returned for payment collection. It stops short of addressing retry billing or the effect of the optional idempotency_key despite idempotentHint=false.

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 delivers the flow stage, cost, and the three possible return states with their key fields, with no redundant phrasing.

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 no output schema, the description carries the return-value burden and does so at a summary level by naming the three states and the salient fields (checkout_url, job_id, report_url). The internal shape of 'structured audit findings' remains unspecified, which is a modest gap for a payment-gated job tool.

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?

Every one of the 5 parameters is already documented in the schema at 100% coverage, and the description adds no format, constraint, or precedence detail (e.g., how image_urls interacts with photos passed at start). Baseline 3 applies when the schema carries all parameter meaning.

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 concrete verb pair ('verify' + 'run or poll') on a named resource ('15-credit Profile Signal Audit'), so an agent knows it both gates on payment and executes/monitors a job. The connection to the sibling citadel_start_profile_upgrade is only implicit (visible through the agent_session_token schema text), so explicit sibling differentiation is absent from the description itself.

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 enumeration of awaiting_payment, processing and complete implies repeated polling until terminal state, but the description never states 'call again' or how to choose between this tool and citadel_get_session_status. Usage is inferable from the state list rather than stated, which is the definition of implied guidance.

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.