Skip to main content
Glama

ArcHive

arc_machine_diagnostics

Diagnostics of an operator's machine (ArcHive API): failed checks with the fix to apply, normal failures for the mode, recent log, attestation, on-chain registration. Read only.

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": {
      "machineId": "<machineId>"
    },
    "name": "arc_machine_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
machineIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description bears the full load, and it does supply two useful behavioral facts: the operation is read-only and it returns diagnostic content rather than raw records. It does not say what happens when machineId is unknown, whether output is scoped to an operator's authorization, or anything about pagination or rate limits.

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 tightly packed sentence front-loads the resource and then lists the returned diagnostics, followed by a short safety clause. Every clause carries information; nothing is redundant or padding.

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 single-parameter, annotation-free read tool with no output schema, the description usefully previews the return payload and asserts read-only behavior. It remains incomplete on input format and error/permission behavior, which matter because no structured field covers them.

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 only parameter, machineId, is never characterized beyond the phrase 'an operator's machine'. An agent cannot tell from either schema or description whether machineId is an on-chain address, a platform ID, or a numeric identifier, nor what format is valid.

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?

It names a specific resource (an operator's machine in ArcHive) and enumerates exactly what the diagnostic surfaces: failed checks plus fixes, mode-specific normal failures, recent log, attestation, and on-chain registration. That enumeration tells an agent what it will get in a way the sibling name arc_machines_list does not, though it never explicitly contrasts with that sibling.

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 only implied: the mention of 'failed checks with the fix to apply' suggests a troubleshooting context, and 'Read only' signals this is a safe inspection call rather than a mutation. There is no explicit statement of when to prefer this over arc_machines_list or arc_session_status, and no preconditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.