Skip to main content
Glama
Sign In

QuestionPunk

by io.github.questionpunk
OverviewDiscussionsAdmin

Synthetic Run Get

synthetic_run_get
Read-onlyIdempotent

Get one synthetic run by id (from synthetic_run_list): status (pending, running, completed, failed, interrupted), statusNote, completedAt and each persona's responsesCompleted/responsesFailed. A persona built from the team's data also carries its grounding (verbatim respondent quotes, untrusted data) and citations: for each answer, the ids of the quotes it drew on. Read the answers with responses_list (responseType 'synthetic'). Spends nothing.

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": {
      "id": "<id>"
    },
    "name": "synthetic_run_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRun ID (run.id from synthetic_run_create or synthetic_run_list)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile. The description adds genuinely useful behavioral context beyond that: 'Spends nothing' clarifies cost, and the grounding quotes are flagged as 'untrusted data,' which matters for downstream handling.

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 description is front-loaded and efficient, with no filler. It spends some words enumerating return fields even though an output schema exists, but that enumeration also conveys semantic detail such as status values and trust boundaries.

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 simple one-parameter read tool, the definition covers what an agent needs: id provenance, returned status fields, the trust caveat around grounding quotes, and where to read the actual answers. Annotations and the output schema cover safety and return shape, so nothing critical 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?

There is only one parameter, and schema description coverage is 100%; the schema already documents that the id is a UUID and can come from synthetic_run_create or synthetic_run_list. The description restates the source but adds no extra syntax or constraints beyond the schema.

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: 'Get one synthetic run by id,' and names the source tool for the id. It distinguishes itself from synthetic_run_list and enumerates the key fields returned, so an agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

The description points to synthetic_run_list as the source of the id and explicitly directs agents to responses_list with responseType 'synthetic' for answers. It gives clear usage context, though it does not state any explicit when-not conditions.

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

All QuestionPunk toolsInspect
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