cdisc-library-mcp-server

sdtm.packages.getSpecialization

Retrieve SDTM dataset specialization details by specifying a package and dataset specialization name. Get the structured representation of a specific specialization within an SDTM package.

Instructions

Get SDTM specialization within a package.

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": {
      "package": "<package>",
      "datasetSpecialization": "<datasetSpecialization>"
    },
    "name": "sdtm.packages.getSpecialization"
  }
}

Input Schema

Name	Required	Description	Default
`package`	Yes
`datasetSpecialization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist. Description does not disclose behavior such as error handling, side effects, authentication requirements, or return value structure.

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?

Extremely concise (one sentence) but lacks necessary detail; under-specification outweighs brevity.

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?

For a simple retrieval tool with two required parameters, no output schema, and no annotations, the description is incomplete—missing return format, error cases, and prerequisite context.

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

Parameters1/5

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

Schema has 0% description coverage for parameters, and the description adds no meaning to 'package' or 'datasetSpecialization', leaving the agent to infer from names alone.

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?

The description clearly states the verb 'Get' and the resource 'SDTM specialization within a package', distinguishing it from sibling 'listSpecializations' which lists all.

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?

No guidance on when to use this tool versus alternatives like listSpecializations, nor any prerequisites or context for invocation.

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