Skip to main content
Glama

predict

Generate predictions from feature records using a previously trained local model artifact, keeping inference on your own machine without cloud services or API keys.

Instructions

Generate predictions using a previously trained local model.

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": {
      "artifact_name": "<artifact_name>",
      "features": "<features>"
    },
    "name": "predict"
  }
}

Input Schema

NameRequiredDescriptionDefault
featuresYesFeature record(s) to predict on.
artifact_nameYesName of the exported model artifact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether inference is local-only/offline, whether it is read-only or has side effects, whether predictions are batched, or what the response contains. 'Local model' hints at no network call but that is the only behavioral signal.

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 well-formed sentence with the key constraint ('previously trained') front-loaded and no filler. It is efficient, though its brevity edges into under-specification rather than crispness.

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?

With no annotations and no output schema, the description is the only place an agent could learn what predictions look like (labels, scores, shapes) and what preconditions apply, and it supplies neither. For an inference tool whose output format is undefined elsewhere, this leaves a material gap.

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 both artifact_name and features are already documented in the schema and a baseline of 3 applies. The description adds only the context that the artifact is a previously trained local model and that features can be records (plural), not new syntax or format detail.

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?

States a specific verb ('Generate predictions') and the resource it operates on ('a previously trained local model'). The phrase 'previously trained' implicitly separates it from train_baseline and export_model, though it never names an alternative or explicitly ties it to the artifact_name parameter.

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, no prerequisite ordering (e.g., that a model must first be exported or trained), and no reference to any sibling such as compare_models or train_baseline. The agent must infer the entire workflow from the single sentence.

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