Skip to main content
Glama

Analyse pull sessions

pull_analyse

Analyses the sessions of one condition (one session, a list, or {"sessions": [...]}) together, and each alone, and returns the report: its label (significant; null, with the smallest effect these sessions could have found; unlabelled, with what is missing; or not testable) and the sentence behind it, the mean signed shift against three surrogate families, the placebos, the four cells (deliberate, programmed, luck and sync), intended against unintended changes, recovery, locking, and the report's hash. prereg registers the run; replication analyses a second set under it, beside the first; measure is phase (timing, the default) or state (the stance along the leader's declared direction, for two agents); surrogates (19 to 9,999, default 199) sets an unregistered run's draws a family, a registered run taking its pre-registration's; seed fixes them; a session of three or more generators is tested pair by pair, every ordered pair with its own ledger and the correction for their number, unless pairs is false; detail adds every pull record. It costs one unit for each 40,000 session-draws over a thousand events (a session's own reading counts as 200 draws), at least 1. A group costs its ordered pairs' worth. A call priced at more than 2 units is queued: the answer is 202 with a job id and its price, GET /api/agents/jobs/ (or the MCP tool job) says when it is done, and the whole report comes back as report.json beside a short verdict. A queued call is refused on the free plan with 402: its units buy only calls that answer at once, and queued jobs need the subscription. Sessions are not kept.

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": {
      "sessions": "<sessions>"
    },
    "name": "pull_analyse"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoA whole number that makes the run reproducible: the same seed and inputs give the same answer.
pairsNoTrue to analyse performer pairs as well.
detailNoTrue to return the fuller per-session detail.
preregNoThe pre-registration the sessions were run under, to check the analysis against it.
measureNoThe measure to analyse, by name.
sessionsYesOne session, a list of sessions, or {"sessions": [...]} of one condition, as JSON documents.
surrogatesNoHow many surrogate runs to draw for the null, 19 to 9999.
replicationNoSessions of a replication, analysed against the first set.

Output Schema

NameRequiredDescriptionDefault
msNoMilliseconds the run took.
jobYesThe job id; the job tool reads it.
verbNoThe tool that made it.
filesNoFiles made, each with a name, type, size and a signed URL.
unitsNoUnits this call cost.
resultNoThe engine's own answer, a JSON document.
statusNoqueued when the job runs in the background.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / detail / description
      Added value: +"True to return the fuller per-session detail."
    • addedInput schema / properties / measure / description
      Added value: +"The measure to analyse, by name."
    • addedInput schema / properties / pairs / description
      Added value: +"True to analyse performer pairs as well."
    • addedInput schema / properties / prereg / description
      Added value: +"The pre-registration the sessions were run under, to check the analysis against it."
    • removedInput schema / properties / replication / $ref
      Removed value: -"#/properties/sessions"
    • addedInput schema / properties / replication / anyOf
      Added value: +[
      +  {
      +    "$ref": "#/properties/sessions/anyOf/0"
      +  },
      +  {
      +    "$ref": "#/properties/sessions/anyOf/1"
      +  }
      +]
    • addedInput schema / properties / replication / description
      Added value: +"Sessions of a replication, analysed against the first set."
    • addedInput schema / properties / seed / description
      Added value: +"A whole number that makes the run reproducible: the same seed and inputs give the same answer."
    • addedInput schema / properties / sessions / description
      Added value: +"One session, a list of sessions, or {\"sessions\": [...]} of one condition, as JSON documents."
    • addedInput schema / properties / surrogates / description
      Added value: +"How many surrogate runs to draw for the null, 19 to 9999."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "files": {
      +      "description": "Files made, each with a name, type, size and a signed URL.",
      +      "items": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "job": {
      +      "description": "The job id; the job tool reads it.",
      +      "type": "string"
      +    },
      +    "ms": {
      +      "description": "Milliseconds the run took.",
      +      "type": "number"
      +    },
      +    "result": {
      +      "description": "The engine's own answer, a JSON document."
      +    },
      +    "status": {
      +      "description": "queued when the job runs in the background.",
      +      "type": "string"
      +    },
      +    "units": {
      +      "description": "Units this call cost.",
      +      "type": "number"
      +    },
      +    "verb": {
      +      "description": "The tool that made it.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "job"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the cost formula (one unit per 40,000 session-draws over a thousand events, minimum 1, with 200 draws for a session's own reading), the asynchronous path (202 + job id, retrieval via GET /api/agents/jobs/<job> or the job tool), the free-plan 402 refusal, and the retention fact 'Sessions are not kept.' These are exactly the operational traits an agent cannot get from the schema. The costs and writes are consistent with readOnlyHint=false and idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Nearly every clause carries real information (pricing, queueing, pair testing, parameter defaults), so the length is largely justified for a tool this complex. However it is delivered as one unbroken semicolon-chained paragraph with no grouping of return values, parameters, and billing, which makes it hard to scan. Front-loading is partial: the action comes first, but the essential cost/queue rules are buried mid-paragraph.

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

Completeness4/5

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

For an eight-parameter tool with an output schema, the definition covers the gaps that matter: cost, queueing, free-plan failure, data retention, and pair-testing behaviour. It spends words re-describing report contents that the output schema likely already provides, but the alternative response shapes (202 job, 402) justify some of that. Nothing an agent needs to invoke it correctly appears to be missing.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds substantive meaning: measure is 'phase (timing, the default) or state (the stance along the leader's declared direction, for two agents)'; surrogates range 19–9,999 default 199 and applies only to unregistered runs, with registered runs inheriting the pre-registration's count; seed fixes the draws; detail adds every pull record. This clarifies defaults, value sets, and conditional applicability that the schema only gestures at.

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?

The opening clause names a specific verb and resource ('Analyses the sessions of one condition') and enumerates the returned report (label, mean signed shift, placebos, cells, recovery, locking, hash), so an agent knows what it gets. It also touches the relationship to pre-registration and replication, though it never explicitly contrasts itself with a named sibling. The jargon density ('the four cells', 'surrogate families') blurs the purpose somewhat.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'prereg registers the run; replication analyses a second set under it' hints at the workflow, and 'pairs is false' / 'detail' describe conditional behaviours. There is no explicit when-to-use-this-vs-alternative statement, no prerequisites beyond the billing/queue rules, and no exclusion guidance. An agent can infer the scenario but must reason it out.

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