Skip to main content
Glama
Sign In
TrueNAS Core MCP Server

TrueNAS Core MCP Server

by vespo92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_pool_status

Retrieve the detailed status of a specific storage pool on the TrueNAS Core MCP Server, enabling efficient monitoring and management of storage resources.

Instructions

Get detailed status of a specific pool

Args:
    pool_name: Name of the pool

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": {
      "pool_name": "<pool_name>"
    },
    "name": "get_pool_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'detailed status' but doesn't specify what that includes (e.g., health metrics, capacity, performance), whether it's a read-only operation, or any constraints like authentication needs or rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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 front-loaded with the core purpose in the first sentence, followed by a concise 'Args' section. Every sentence earns its place with no wasted words, making it efficient and well-structured for quick understanding.

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

Completeness2/5

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

Given the complexity of a status-checking tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed status' entails, the return format, or any behavioral traits like error handling. This makes it inadequate for an agent to fully leverage the tool without additional context.

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?

The schema description coverage is 0%, but the description includes an 'Args' section that documents the single parameter 'pool_name' with a brief explanation. This adds value beyond the bare schema, though it's minimal and doesn't cover format or examples. With one parameter, the baseline is 4, but the limited detail reduces it to 3.

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 clearly states the verb 'Get' and the resource 'detailed status of a specific pool', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_pools' or 'get_system_info', which might also provide pool-related information, so it doesn't reach the highest score.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list_pools' for a broader view or 'get_system_info' for general system status. The description only states what it does without context for selection among siblings.

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

Deploy Server

Other Tools

Related Tools