Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

disk_capabilities

Read-onlyIdempotent

Reports the host adapter's actual disk operations and advertised filesystem constraints, so agents can verify capabilities separately from the reference compatibility database.

Instructions

Report this host adapter's actual disk operations and advertised filesystem constraints. This is separate from the reference compatibility database.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered by structured data. The description's contribution is the "actual host adapter vs. reference database" distinction, which is genuine added context. It does not describe the shape or richness of the report, and with no output schema that is a remaining 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?

Two sentences, no filler, with the core purpose stated first and the disambiguating contrast second. Every clause carries information and nothing is repeated from the annotations or schema.

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 zero-argument, read-only reporting tool the calling decision is simple, and annotations cover safety. But with no output schema, the description is the only source of information about what comes back, and "actual disk operations and advertised filesystem constraints" is too abstract for an agent to anticipate the returned fields. Adequate, not complete.

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 and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the result is host-specific and takes no scoping input.

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 uses a specific verb ("Report") and scopes the resource to "this host adapter's actual disk operations and advertised filesystem constraints," which is a meaningful distinction from generic disk inspection siblings like disk_details. However, "disk operations" stays abstract — it never says whether that means supported opcodes, mount flags, or capability bits, so the agent knows the topic but not the content.

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?

The second sentence establishes a usage boundary — this reports live adapter reality rather than the reference compatibility database — which implicitly routes the agent away from filesystem_compatibility-style tools. It stops short of stating when to prefer this over disk_details or filesystem_compatibility by name, so the guidance is inferable but not explicit.

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