kirimi-mcp

device_status_enhanced

Retrieve detailed device status with today and total message statistics to monitor messaging activity and device health.

Instructions

Get detailed device status, including today and total message statistics.

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": "device_status_enhanced"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	No	Device ID (e.g. D-XXXXX). Optional if the KIRIMI_DEVICE_ID environment variable is set.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Sep 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states the action is a read ('Get'), implying no side effects, but it does not disclose any potential latency, prerequisites (e.g., device must be online), or output structure. It is not misleading, but it adds minimal behavioral context beyond the action itself.

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?

The description is a single, concise sentence that front-loads the core purpose and the key differentiator (message statistics). There is no redundant wording or filler.

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?

The tool is simple with one optional parameter and no output schema, but the description does not specify the exact format of the returned statistics or any error conditions. It mentions 'today and total message statistics' but not how they are presented. For an agent to use the result effectively, more detail might be helpful, though the description is adequate for a basic status retrieval.

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?

The input schema has 100% coverage for the single parameter device_id, including a note about the environment variable fallback. The description adds no additional meaning to the parameter, so the baseline score of 3 applies; the schema already documents it adequately.

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?

The description clearly states the verb 'Get' and the resource 'detailed device status', and specifies the distinguishing feature: today and total message statistics. This differentiates it from the sibling device_status tool, making the purpose unambiguous.

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 guidance on when to use this tool versus the basic device_status or other alternatives. It does not mention that basic status queries might use device_status, nor any conditions for choosing this enhanced version. The only implied usage is from the name, but that is not explicit.

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