Skip to main content
Glama

fit_status

Retrieve the status, progress stage, errors, and timestamps of a conjoint model fit to monitor queued, running, completed, failed, or cancelled jobs.

Instructions

A fit's status (queued, running, done, failed, cancelled), progress stage, error and timestamps.

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": {
      "fit_id": "<fit_id>"
    },
    "name": "fit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fit_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value by enumerating the terminal and in-flight status values (queued, running, done, failed, cancelled) plus the presence of an error field and timestamps. However, it says nothing about read-only/side-effect behavior, authentication, or whether repeated calls are cheap, which matters for a polling tool.

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 tight fragment that front-loads the return payload with no filler. It is efficient, though it is a bare noun phrase rather than a directive sentence, which slightly weakens actionability.

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?

With no output schema, the description is right to enumerate returned fields, and it does so competently. What is missing is the operational context an agent needs: whether the call blocks, how it differs from wait_for_fit, and how a fit_id is obtained.

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 coverage is 0% and the single parameter fit_id is documented only as a string, yet the description never explains where a fit_id comes from or its format. The surrounding noun phrase ('a fit's status') at least implies the parameter identifies the fit, so it is not fully uninformative, but it adds almost nothing beyond the schema.

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 names the resource (a fit) and precisely what it returns: status values, progress stage, error, and timestamps. It is clear this is a status-retrieval tool, but the verb is implicit in the noun phrase and it never distinguishes itself from the closely related wait_for_fit sibling, which likely serves a similar polling purpose.

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 at all. In a catalog containing start_fit, cancel_fit, and wait_for_fit, an agent cannot tell from this description whether fit_status is a one-shot non-blocking check or a polling call, and no condition selects it over wait_for_fit.

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