trmm-mcp

trmm_agent_checks

Read-onlyIdempotent

Get the current status of all checks configured on a specified agent, with an option to list only failing checks.

Instructions

Checks configured on an agent, with their current status.

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": {
      "agent": "<agent>"
    },
    "name": "trmm_agent_checks"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	Yes
`failing_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 4, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that statuses are included in the result, which is useful but minimal context beyond the annotations.

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 compact sentence with no filler or redundancy. It front-loads the resource and adds the key output dimension without wasting words.

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?

For a low-complexity read-only tool with strong annotations, this is minimally viable. However, there is no output schema and the description does not explain what a 'check' looks like or how statuses are represented, so the agent must infer some important details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the agent identifier format or the meaning of failing_only beyond what the parameter names imply. The 'agent' parameter is somewhat self-explanatory from the description, but 'failing_only' semantics are left to inference.

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 identifies the resource ('checks configured on an agent') and indicates that current status is included. It lacks an explicit verb like 'list' or 'get', but the meaning is unmistakable and it is distinct from sibling tools such as agent_services or agent_processes.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It relies entirely on the tool name and sibling context to imply its role.

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