mcp-fabric-api

ml_experiment_get

Read-only

Get details for a specific ML experiment by supplying workspace ID and experiment ID, enabling quick access to experiment metadata and status.

Instructions

Get details of a specific ML experiment

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": {
      "workspaceId": "<workspaceId>",
      "mlExperimentId": "<mlExperimentId>"
    },
    "name": "ml_experiment_get"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID
`mlExperimentId`	Yes	The ML experiment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Get' aligns with that. The description adds no additional behavioral context, such as what fields are returned, authentication requirements, or edge cases. It is consistent but does not go beyond the annotations.

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. It directly states the operation and the resource, making it efficient and easy to parse.

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

Completeness3/5

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

The description is sufficient for basic invocation given the two documented parameters and safety annotations. However, with no output schema, the term 'details' is vague and does not clarify what the response will contain, and there is no mention of prerequisites like obtaining the experiment ID.

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%, with both workspaceId and mlExperimentId described in the schema. The description adds no extra meaning beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Get') and a specific resource ('details of a specific ML experiment'). It clearly distinguishes itself from sibling tools like ml_experiment_list (which lists experiments) and ml_experiment_update/delete (which mutate experiments).

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?

No explicit guidance is given on when to use this tool versus ml_experiment_list, nor how to obtain the mlExperimentId (e.g., from a list call). The usage is implied by the name and description, but no alternatives or exclusions are mentioned.

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

Deploy Server