Skip to main content
Glama
io.github.xngg1021/academic-research-kernel

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_scfabric_hardware_probe

Detects available local hardware accelerators such as CUDA, ROCm, MPS, and XPU and reports execution environment details to verify setup before running research workflows.

Instructions

Probe local hardware accelerators (CUDA, ROCm, MPS, XPU) and execution environments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and discloses very little: it does not say whether probing is read-only, whether it shells out to driver utilities, how long it may block, or whether it can fail or warn on missing drivers. "Probe" implies a safe inspection, but that is inference, not disclosure.

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?

A single front-loaded sentence with no filler or redundancy. Nothing could be removed without losing information.

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 no-arg, no-output-schema tool, the description should indicate what the probe reports back (available devices, versions, availability flags) so the agent knows what it will get. Without an output schema, not explaining the return shape leaves a meaningful gap for a capability-discovery tool.

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, so there is nothing for the description to disambiguate; the baseline for a no-arg tool applies. The enumerated backend list is a minor plus because it tells the agent what the (implicit) scope of the probe is.

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 gives a specific verb ("Probe") and resource ("local hardware accelerators ... and execution environments") and enumerates the backends it covers (CUDA, ROCm, MPS, XPU). An agent can tell at a glance this is about discovering local compute capabilities, though it offers no differentiation from the similarly academic_* siblings.

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 call this versus anything else, no prerequisites, and no statement about whether it should be run before configuring or benchmarking other tools. The agent is left to infer usage entirely from the one-line purpose.

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