Skip to main content
Glama
Sign In
SensorForge MCP Server

SensorForge MCP Server

by sidupreti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Run status

run_status
Read-only

Check a model fit or optimization run's current status without waiting: queue position, live progress, or final verdict with before-and-after SRAM, flash, and accuracy.

Instructions

The state of a run right now, without waiting: queued (with its place in line), running (with its latest progress), or finished with the verdict and the before -> after SRAM, flash and accuracy.

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": {
      "run_id": "<run_id>"
    },
    "name": "run_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run id from check_fit, lossless, optimize or list_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds real behavioral value: the call is non-blocking, and the three response states with the data attached to each are disclosed. It does not say what happens for an unknown, expired, or still-queued-but-cancelled run id, so it is not fully transparent.

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 front-loaded sentence using a colon and parentheticals to enumerate outcomes, with no redundant restatement of the title. It is dense but every clause carries information; a slightly cleaner breakdown of the three states would be marginally clearer.

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?

No output schema exists, so the description correctly carries the return-shape burden by naming the state variants and their payloads. Given a one-parameter read tool, this is close to complete; only error and edge-case behavior (invalid or expired run id) is left unstated.

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?

There is a single parameter with 100% schema description coverage, and the schema already tells the agent that run_id comes from check_fit, lossless, optimize, or list_runs. The description itself adds no further meaning about the identifier, so the baseline of 3 applies.

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-resource pair: returns the current state of a run, non-blocking, and enumerates the three possible outcomes (queued with position, running with latest progress, finished with verdict and before/after SRAM, flash, accuracy). That distinguishes it from a blocking poller, though it never names the sibling it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'right now, without waiting' clearly signals the polling/non-blocking use case, which implicitly separates it from a wait-for-completion tool. It does not explicitly say when not to use it or name the alternative to pick instead, so it stops short of full routing guidance.

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