Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ai_detection_status

Read-onlyIdempotent

Report whether the Max4's AI failure detection for spaghetti and foreign objects is enabled, its sensitivity, and the last camera verdict. Read-only; check enabled flags before trusting zero counts.

Instructions

Report the Max4's AI failure detection: whether spaghetti ('noodle') and foreign-object detection are enabled, their sensitivity, and the last verdict the camera service reported. Read-only. Note a zero count from a DISABLED detector means 'nothing ever reported', not 'the bed is clear' -- check the enabled flags before trusting it as evidence of anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ai_detection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly and idempotent, and the description's 'Read-only' is redundant. It earns credit beyond the annotations by disclosing a non-obvious semantic trap: a zero count from a disabled detector means 'nothing ever reported', not 'bed is clear'. That is exactly the kind of interpretive context annotations cannot carry.

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?

Front-loaded with the purpose, then the reported fields, then the caveat — a sensible order. The redundant 'Read-only.' sentence costs a little, and the em-dash caveat is long, but every clause carries real information.

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 zero-argument read with an output schema, the description covers what an agent needs: what is reported and the main interpretive pitfall. It could add one line on the relationship to set_ai_detection, but no essential information is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description also names the domain-specific fields being reported, which helps orient the agent to the output.

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

Purpose5/5

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

States a specific verb and resource ('Report the Max4's AI failure detection'), enumerates exactly what is reported (spaghetti/noodle and foreign-object enablement, sensitivity, last verdict), and is clearly distinguishable from the sibling set_ai_detection by being a report rather than a mutation.

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?

Usage is implied by the reporting verb and the closing caution about when to trust a zero count, but the description never names set_ai_detection as the counterpart for changing these settings or states a prerequisite/sequence (e.g. check here before or after configuring). Guidance is present but indirect.

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