Skip to main content
Glama

Run full check

upgrade_to_full_review
DestructiveIdempotent

Run the full check on a finished preliminary check: exact 0–100 score, scores for six categories (hook, story, offer, audience, picture, sound), every issue with severity and timecodes, prioritized fixes and strengths. Uses 1 token from the balance of the user's Quelta account (a new account gets 1 free token) — confirm with the user first; calling it again for the same analysis does not use another one. Takes 1–3 minutes: if not finished within ~40 seconds, returns status 'processing'; get_analysis returns the result.

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": {
      "analysis_id": "<analysis_id>"
    },
    "name": "upgrade_to_full_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
analysis_idYesThe analysis_id of a finished preliminary check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the cost model (1 token from the Quelta balance, 1 free token for a new account), the idempotent billing behavior (repeat calls for the same analysis don't consume another token), and the async latency profile (~40 seconds before returning 'processing', 1–3 minutes total). These details are consistent with destructiveHint=true and idempotentHint=true rather than contradicting them, and they add real operational context an agent cannot get from the annotations alone.

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?

The output contents are front-loaded and every sentence carries information: cost, confirmation, billing idempotency, latency, and the follow-up tool. It is a single dense run-on paragraph with em dashes, which makes it slightly harder to scan than a short bulleted structure would, but there is no filler.

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

Completeness5/5

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

There is no output schema, so the description must describe the return payload, and it does — score, six category scores, issues with severity and timecodes, fixes and strengths — plus the 'processing' status path and the get_analysis handoff. For a one-parameter, token-consuming async analysis tool, an agent has everything needed to call it and handle the response.

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 description coverage is 100% and the single parameter's schema text ('The analysis_id of a finished preliminary check') already carries the key constraint, so the description's mention of a 'finished preliminary check' largely duplicates it. No additional detail on ID format or where to obtain an analysis_id is provided. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb+resource ('Run the full check on a finished preliminary check') and enumerates exactly what the result contains: a 0–100 score, six named category scores (hook, story, offer, audience, picture, sound), issues with severity and timecodes, prioritized fixes and strengths. It is clearly differentiated from the sibling upgrade_product_check and from analyze_video_ad by tying the call to a finished preliminary check.

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

Usage Guidelines5/5

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

The preconditions and routing are explicit: the target must be a finished preliminary check, the user must be asked to confirm because a token is consumed, and if the call returns status 'processing' the agent should switch to get_analysis. When-to-use, when-to-confirm, and which alternative to call next are all stated rather than implied.

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.

Resources