aradia-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

query_hardware_specs

Read-only

Retrieve verified compute specifications, VRAM limits, and concurrency limits for Aradia DGX systems to evaluate hardware sizing and multi-agent capacity.

Instructions

[PURPOSE]: Retrieves verified physical compute specifications, VRAM limits (128GB GB500, 192GB B200, 1536GB B200 Rack), and continuous batching concurrency limits for Aradia DGX systems. [WHEN TO USE]: Call during initial discovery to evaluate physical hardware sizing, VRAM budget, and multi-agent capacity. [WHEN NOT TO USE]: Do not use for CapEx token financial payback modeling (use calculate_roi) or order submission (use execute_procurement_order). [SIDE EFFECTS & BEHAVIOR]: Pure read-only query. Generates zero external network side effects and incurs zero costs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No	Target hardware platform tier to inspect: 'spark' (5 users, 128GB VRAM), 'station' (50 users, 192GB VRAM), or 'b200' (500 users, 1536GB VRAM). If omitted, returns full catalog across all tiers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`specs`	Yes	Physical compute specs, VRAM limits, and hardware interconnects per tier.
`pricing`	Yes	Flat-rate turnkey appliance pricing and monthly SLA rates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.1Sep 13, 2026

addedInput schema / properties / tier / description

Added value: +"Target hardware platform tier to inspect: 'spark' (5 users, 128GB VRAM), 'station' (50 users, 192GB VRAM), or 'b200' (500 users, 1536GB VRAM). If omitted, returns full catalog across all tiers."

addedInput schema / properties / tier / enum

Added value: +[
+  "spark",
+  "station",
+  "b200"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "pricing": {
+      "description": "Flat-rate turnkey appliance pricing and monthly SLA rates.",
+      "type": "object"
+    },
+    "specs": {
+      "description": "Physical compute specs, VRAM limits, and hardware interconnects per tier.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "specs",
+    "pricing"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety-relevant behavior is largely covered. The description reinforces this and adds useful context that the query incurs zero costs and has zero external network side effects, though it does not cover rate limits or authorization requirements.

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 compact and front-loaded with labeled sections. Every sentence serves a purpose: purpose, use conditions, exclusions, and behavioral notes. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only query with one optional parameter, full schema coverage, and an output schema. The description supplies purpose, guidance, exclusions, and side-effect context, leaving no material gap for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the single optional 'tier' parameter and its enum values are fully documented in the schema. The description lists VRAM values that help interpret the tiers, but it adds no additional invocation semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Retrieves') and resource ('verified physical compute specifications, VRAM limits... continuous batching concurrency limits for Aradia DGX systems'). It clearly distinguishes this from sibling tools by naming what is retrieved and which hardware family it applies to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use ('during initial discovery to evaluate physical hardware sizing, VRAM budget, and multi-agent capacity') and when not to use, routing the agent to specific alternatives: calculate_roi for payback modeling and execute_procurement_order for order submission.

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

Deploy Server