Skip to main content
Glama

resubmit_ecc_probe

Re-queues an ECC probe/sensor by resetting its ecc_queue state to ready to retry stalled or failed probes. Requires WRITE_ENABLED=true.

Instructions

Re-queue an ECC probe/sensor by setting its state back to ready (ecc_queue). Requires WRITE_ENABLED=true

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": {
      "sys_id": "<sys_id>"
    },
    "name": "resubmit_ecc_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYessys_id of the ecc_queue record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive operation, so the bar is lower; the description still adds material context by explaining the actual state mutation performed and the WRITE_ENABLED gate the caller must satisfy. It does not address what happens to an in-flight or currently-running probe, which is the main remaining behavioral gap.

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?

One compact sentence plus a short precondition clause; the action is front-loaded and every word contributes information. Nothing could be removed without losing meaning.

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 one-parameter mutation with no output schema, the description covers the action, the target table, the state change, and the required environment flag. Completeness would be higher if it stated the effect of repeated calls given the non-idempotent hint, or what a success/failure looks like.

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 required parameter with 100% schema description coverage, so the schema already explains sys_id fully. The description only restates that the record is an ecc_queue row, adding no format, lookup, or validation detail 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 a specific verb ('Re-queue'), a specific resource ('ECC probe/sensor'), and the underlying mechanism ('setting its state back to ready') on the ecc_queue table. This clearly separates it from the read-only get_ecc_queue sibling, though it never names that sibling explicitly.

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?

It provides a precondition ('Requires WRITE_ENABLED=true'), which is genuine usage guidance, but it never states when to re-queue versus when a probe should be left alone or handled another way, and no alternative tool is referenced. Usage context is implied rather than spelled out.

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