QuestionPunk

Prolific Study Get

prolific_study_get

Read-onlyIdempotent

Get one Prolific study's live details by studyId (the id from prolific_study_list): status, submissions, places, screener filters, devices, content warnings, and reward and costs in dollars (not cents). Only the survey's owner can read it. Returns no participant data.

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": {
      "surveyId": "<surveyId>",
      "studyId": "<studyId>"
    },
    "name": "prolific_study_get"
  }
}

Input Schema

Name	Required	Description	Default
`studyId`	Yes	QuestionPunk's Prolific study ID: `prolificStudy` from prolific_study_create_draft or `id` from prolific_study_list (not `prolificStudyId`, which is Prolific's own ID)
`surveyId`	Yes	The survey ID (not used for the lookup)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds useful context beyond annotations: owner-only visibility, no participant data returned, live details, and reward/cost values expressed in dollars rather than cents.

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?

Front-loads the core action and packs necessary details into a single dense sentence. The field enumeration is useful but slightly list-heavy; overall there is little wasted wording.

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 read-only tool with annotations and an output schema, the description covers the remaining essentials: authorization scope, absence of participant data, id provenance, and unit semantics for monetary fields.

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%, with detailed descriptions clarifying studyId versus prolificStudyId and noting surveyId is not used for lookup. The description reinforces the studyId source but adds little to the already-complete schema; baseline 3 is appropriate.

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 Prolific study's live details by studyId. It enumerates the exact fields returned (status, submissions, places, filters, devices, warnings, reward/cost units) and explicitly ties the id to prolific_study_list, distinguishing it from list operations.

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?

Clearly establishes the lookup key comes from prolific_study_list and notes the owner-only access constraint. It does not explicitly compare against alternatives like prolific_study_list or explain when not to use it, but the context is strong enough for correct selection.

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

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