Skip to main content
Glama

citadel_evaluate_profile_readiness

Read-onlyIdempotent

Evaluate dating profile structural readiness and estimate first-impression conversion bottlenecks from photo count, group-photo ratio, and prompt length.

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": {
      "photoCount": "<photoCount>",
      "soloClearLeadPhoto": "<soloClearLeadPhoto>"
    },
    "name": "citadel_evaluate_profile_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
photoCountYesTotal number of photos in the profile (1-6)
promptCountNoNumber of completed written prompts or bio sections (0-3)
soloClearLeadPhotoYesWhether Slot #1 is a clear, solo, unobstructed portrait without sunglasses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description usefully signals that results are an 'estimate' of conversion bottlenecks rather than a definitive judgment, but it does not describe output shape, scoring scale, or whether the evaluation is deterministic, despite there being no output schema.

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?

A single front-loaded sentence with the outcome stated before the inputs; no filler. It loses a point only because the input enumeration it spends half its length on is partly inaccurate.

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

Completeness3/5

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

For a 3-parameter, read-only, closed-world evaluator with full schema coverage and annotations, the essentials are present. However, with no output schema, the description should say more about what comes back (a readiness score? a ranked bottleneck list?) and should not invent input names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description actively mismatches the schema: it cites 'group-photo ratio' as an input, which is not a parameter, and says 'prompt length' where the schema defines promptCount (a count, not a length). It also omits the critical soloClearLeadPhoto slot requirement. The description therefore adds confusion rather than 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?

Names a specific verb and resource: 'Evaluate dating profile structural readiness' plus the secondary output 'estimate first-impression conversion bottlenecks.' An agent understands what it computes, but nothing distinguishes it from the sibling citadel_run_or_poll_profile_audit, which plausibly does something similar.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as citadel_run_or_poll_profile_audit or citadel_get_lead_photo_rubric. Usage is only implied by the verb 'evaluate,' leaving the agent to guess when this pre-check is preferable to a full audit.

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.