Skip to main content
Glama

Roc Curve

roc_curve

Plot and save ROC curves for a trained classification model on test data, with one-vs-rest curves for multiclass models and AUC scores per class.

Instructions

Generate and save the ROC curve of a classification model on its test data. Binary models get one curve; multiclass models get one-vs-rest curves. Args: model_id (str): ID of the trained classification model. Returns: dict: Model ID, AUC score per class, and saved image filename.

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": {
      "model_id": "<model_id>"
    },
    "name": "roc_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully states that an image is saved, describes binary versus multiclass curve behavior, and lists the return contents. It does not disclose where the file is saved, whether existing files are overwritten, permission requirements, or failure behavior.

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?

The description is compact and front-loaded, stating purpose first and then behavior and return details. The Args and Returns sections are brief and every sentence adds useful information without repetition.

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?

For a simple one-parameter tool with no output schema, the description does a good job explaining the return dictionary contents and the saved image artifact. It is slightly incomplete because it does not say where the image is saved or what errors may occur, but overall it is adequate.

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

Parameters4/5

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

The schema has zero description coverage for the single parameter, so the description must compensate. It explains that model_id identifies a trained classification model, which is meaningful context beyond the schema's bare string type. Given that there is only one parameter, this is nearly sufficient, though the expected ID format is not specified.

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

Purpose4/5

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

The description gives a specific verb and resource: generate and save the ROC curve of a classification model on its test data. It also clarifies binary versus multiclass behavior. It does not explicitly differentiate this tool from nearby curve tools such as precision_recall_curve or learning_curve, so it falls short of a 5.

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 usage context is implied: this is for classification models evaluated on test data, with one-vs-rest handling for multiclass models. However, there is no explicit guidance on when to choose this over precision_recall_curve or learning_curve, nor any stated prerequisites beyond the model being trained.

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

Deploy Server

Other Tools