Skip to main content
Glama

get_qa_orchestration

Read-onlyIdempotent

Inspect a retained QA session's current step, next action, and model policy without altering it or extending TTL; expired sessions must be restarted.

Instructions

Read a session's current content-free state without changing it.

Use this only to inspect a retained session's current step, next action, and model policy. Reads do not extend the TTL; an unknown or expired session cannot be recovered here, so start a new one. Use advance_qa_orchestration to change an active run or finish_qa_orchestration to record its final outcome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesSession identifier returned by start_qa_orchestration: qar- followed by 32 lowercase hexadecimal characters. Reuse it for this session; do not invent or transform it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYes
statusYes
read_onlyNo
task_typeYes
expires_atYes
next_actionYes
current_stepYes
model_policyNo
allowed_bundlesNo
current_profileNo
deep_assessmentNo
review_profilesNo
selected_bundleNo
allowed_profilesNo
deep_reason_codeNo
selected_profileNo
completed_profilesNo
host_owns_decisionsNo
recommended_bundlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / run_id / description
      Added value: +"Session identifier returned by start_qa_orchestration: qar- followed by 32 lowercase hexadecimal characters. Reuse it for this session; do not invent or transform it."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds real behavioral context beyond them: reads do not extend the TTL, expired or unknown sessions are unrecoverable through this tool, and the state inspected is content-free. These are non-obvious operational traits an agent needs.

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 what the tool does, then immediately adds the critical constraint (no TTL extension, no recovery) and routing to alternatives. Three tight sentences, zero 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?

With an output schema present, return values need no explanation; the description instead covers the runtime semantics an agent can't get from structured fields (TTL behavior, expired-session failure mode, when to use siblings). Complete for a single-parameter read 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?

Schema coverage is 100% and the run_id pattern/format is fully documented in the schema itself, so the description adds nothing about the parameter. Baseline 3 is appropriate when the schema does all the work.

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 ('Read a session's current content-free state'), plus the exact fields returned (current step, next action, model policy). It is immediately distinguishable from siblings named in the text (advance_qa_orchestration, finish_qa_orchestration).

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?

Explicitly scopes usage ('only to inspect a retained session'), names the two alternatives and what each is for, and states the negative case ('an unknown or expired session cannot be recovered here, so start a new one'). Nothing is left to inference.

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