SurveysAI Qualitative Analysis – interview and focus group analysis

Retry failed analysis work

qualitative_retry_analysis

Idempotent

Retries the failed work of an analysis at no charge. Use it only when qualitative_get_run shows retry_available true (action_required retry_or_cancel), and after the user agreed. Requires an API key with the runs:write scope, and the key's owner must own the analysis. On an analysis that has not failed it answers a conflict error. It does not re-run a finished analysis: for a new analysis use qualitative_start_analysis. Afterwards poll with qualitative_get_run.

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": {
      "run_id": "<run_id>"
    },
    "name": "qualitative_retry_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes	The analysis id (`run_id`) from qualitative_list_runs or qualitative_start_analysis.
`idempotency_key`	No	Optional key (printable ASCII, at most 255 characters). Pass idempotency_key to make your own retries safe: repeating the call with the same key returns the original result instead of acting again. If omitted, every call gets its own fresh key.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing billing impact ("at no charge"), auth requirements (runs:write scope, key owner must own the analysis), and the failure mode (conflict error on a non-failed analysis). These are exactly the operational facts an agent needs before invoking a mutation.

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?

Front-loads purpose, then preconditions, then authorization, then error behavior, then follow-up in a tight sequence. Every sentence carries distinct information with no repetition of the title or schema.

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?

For a two-parameter mutation with no output schema, the description covers preconditions, permission requirements, error behavior, and what to do afterwards (poll qualitative_get_run). Nothing material for correct invocation is missing.

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%, so both run_id and idempotency_key are fully documented in the schema, including the idempotency semantics. The description adds no parameter-level detail beyond that, which is acceptable given the schema does the work, but it is not additive.

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 and resource ("Retries the failed work of an analysis") plus a distinguishing property ("at no charge"). It clearly differentiates itself from qualitative_start_analysis by noting it "does not re-run a finished analysis", so an agent can pick the right tool without opening another schema.

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?

Gives an explicit precondition chain: only when qualitative_get_run shows retry_available true with action_required retry_or_cancel, and only after the user agreed. It also names the alternative for the non-retry case (qualitative_start_analysis for a new analysis) and the follow-up action (poll with qualitative_get_run).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SurveysAI Qualitative Analysis – interview and focus group analysis tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?