MCP Machine Learning Agent

get_sample_input

Provides a held-out test-set patient as ready-to-use input_data for predict tools, plus the patient's true diagnosis for validating predictions.

Instructions

Return one test-set patient as a ready-to-use input_data dictionary for the predict tools, along with that patient's true diagnosis.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sample_input"
  }
}

Input Schema

Name	Required	Description	Default
`index`	No	Row of the held-out test set to return.
`test_size`	No	Fraction of the data held out for testing.
`request_id`	No	Your own id for this call; recorded in the audit log.	unknown
`random_state`	No	Random seed for the train/test split.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the two things returned (an input_data dict and the true diagnosis), but says nothing about determinism of the split, bounds/error behavior for index, or the audit-logging behavior implied by request_id. Adequate but thin for an unannotated tool.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the key output ('ready-to-use input_data dictionary') leads and the secondary return ('true diagnosis') follows. Nothing is wasted.

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?

An output schema exists, so return-value explanation is not required, and the schema fully documents parameters. The description is complete enough for a simple fetch tool, with only a minor gap around how index/test_size/random_state jointly determine the returned row.

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 description coverage is 100%, so all four parameters are already documented in the schema, setting the baseline at 3. The description adds no syntax, format, or interaction details beyond the schema, so it neither compensates nor detracts.

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 (return) and resource (one test-set patient as an input_data dictionary plus the true diagnosis), and names its audience explicitly ('for the predict tools'), which cleanly separates it from the predict_* siblings that consume that dictionary.

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?

The description implies usage by tying the output to 'the predict tools', so an agent can infer this is a setup/example-fetching step before prediction. However, it gives no explicit when-to-use statement, no guidance on choosing index/test_size/random_state consistently with the split, and no exclusions.

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

Deploy Server