Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

filesystem_compatibility

Read-onlyIdempotent

Query a sourced Windows/macOS filesystem matrix for native OS support and separate it from computer access, toolkit adapter support, and DJ-player compatibility.

Instructions

Query the sourced native Windows/macOS filesystem matrix. Computer access, toolkit adapter support, and DJ-player compatibility are distinct.

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

Input Schema

NameRequiredDescriptionDefault
platformNo
filesystemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only 'sourced' (a hint at data provenance) and nothing about whether this is a static reference table, what the result contains, or how the matrix is scoped. With the annotation bar already low, the description still contributes very little beyond it.

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?

Two short sentences, front-loaded with the core action, and no filler. The second sentence is terse and slightly cryptic ('distinct' from what?), but it does earn its place by scoping the tool away from adjacent compatibility questions.

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 two-parameter, zero-required, read-only lookup with no output schema, the description is adequate but thin: it does not state what the returned matrix looks like or what a caller should do when 'filesystem' is omitted entirely. Since no output schema exists, some hint about the return values would have been useful. Acceptable minimum rather than complete.

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%, so the description must carry parameter meaning and does not: it never says what 'platform' expects (the enum restricts to windows/macos, though the description's 'Windows/macOS' does loosely mirror that) and never enumerates or exemplifies valid 'filesystem' values, which are a free-form string capped at 64 chars. An agent cannot infer from the description whether 'filesystem' means 'NTFS'/'exFAT'/'APFS' or an arbitrary identifier. This is a meaningful gap for a lookup tool whose whole value depends on valid keys.

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?

States a specific verb+resource: 'Query the sourced native Windows/macOS filesystem matrix', which tells the agent this returns compatibility facts keyed by platform and filesystem. It also explicitly separates itself from DJ-player compatibility lookups, so it is distinguishable from dj_model_compatibility. The only weakness is that 'matrix' is jargon and the exact shape of the answer is left implicit.

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 sentence 'Computer access, toolkit adapter support, and DJ-player compatibility are distinct' implies this tool is for filesystem/computer-access questions only and routes DJ-player questions elsewhere. However, it never explicitly names an alternative tool, nor does it say when to prefer this over disk_capabilities, prepare_native_format, or disk_details, all of which sound adjacent. Usage is implied rather than stated.

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