nrly

by JMoak

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_study_cases

Page public development cases and expectations for a study, excluding held-out cases.

Instructions

Page public development cases and expectations; never returns held-out cases.

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": {
      "study_id": "<study_id>"
    },
    "name": "get_study_cases"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`study_id`	Yes
`input_limit`	No
`input_offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does reveal two behaviors — results are paginated and held-out cases are never included — but says nothing about ordering, authorization or study_id requirements, behavior on an unknown study, or cost of large pages, which leaves a 5-parameter tool largely opaque.

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?

A single front-loaded sentence with no filler, so it is efficient and easy to scan. The terseness is a coverage problem rather than a verbosity problem, so structure itself is sound.

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

Completeness2/5

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

An output schema exists, so return values need not be described. But with 0% schema description coverage, no annotations, and two pairs of overlapping pagination parameters, the description is not complete enough for an agent to call this confidently.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, and the description only implies that limit/offset-style paging exists. It adds no meaning for study_id, and critically does not explain how limit/offset differ from input_limit/input_offset, which is the highest-risk ambiguity in this schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Page' and resource 'public development cases and expectations' identify a paginated listing over study cases, which is more specific than a tautology. However, 'cases and expectations' is undefined and the description never distinguishes this list endpoint from siblings such as get_study_case_spec or get_study_case_messages.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this before get_study_case_spec, or in which workflow (reviewing a study, picking a case) it belongs. The only usage-adjacent statement is the exclusion of held-out cases, which is a scope constraint rather than guidance on choosing this tool.

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