Skip to main content
Glama

citadel_get_session_status

Read-onlyIdempotent

Retrieve unified A-to-Z session state: Stripe payment status, wallet credit balance, staged photo count, Profile Audit report/findings, and generated Forge photos.

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

Input Schema

NameRequiredDescriptionDefault
roast_idNoOptional roast_id filter
agent_session_tokenYesSession token returned by start, audit, or forge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, repeatable read. The description adds the useful fact that the response aggregates five distinct state domains in one call. It does not disclose what happens for an unknown/expired token, whether individual sections can be null when a stage has not been reached, or any polling guidance, which are the traits that would earn a 4 or 5 here.

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?

One sentence, front-loaded with the verb and scope, with the payoff (the enumerated state domains) immediately after. Every clause carries information; nothing is redundant with the name or annotations.

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 it does so by listing the five sections an agent can expect. It falls short on state semantics (nullability, partial sessions, polling cadence), which matter for a status tool, but annotations cover the safety profile and the schema covers inputs, so the remaining gap is modest.

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 both parameters (agent_session_token, roast_id) are already documented in the schema. The description adds no extra meaning about the optional roast_id filter or what it scopes, so the baseline of 3 applies.

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?

A specific verb ('Retrieve') plus a precisely scoped resource ('unified A-to-Z session state'), followed by an enumeration of the domains covered (Stripe payment, wallet credit, staged photos, audit findings, Forge photos). That enumeration is what separates it from single-purpose siblings like citadel_run_or_poll_profile_audit or citadel_platform_status, though no sibling is named outright.

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?

Usage is only implied: 'unified A-to-Z' suggests this is the one-stop status check instead of calling several tools. There is no explicit when-to-use, when-not-to-use, or statement about the right moment to poll (e.g., after start_profile_upgrade or after an audit completes).

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.