Skip to main content
Glama
Sign In
SprutHub MCP Server

SprutHub MCP Server

by pikerr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sprut_get_hub_info

Retrieve the SprutHub controller's name, model, firmware version, and online status to check hub identity and availability.

Instructions

Get general information about the SprutHub controller (name, model, firmware version, online status).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a safe read with no side effects, which is reasonable for a zero-parameter tool, but it does not explicitly state read-only behavior, permission requirements, or whether the call hits the network/hub synchronously.

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 the verb, resource, and payload all in the first clause. No filler or redundancy.

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

Completeness4/5

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

With an output schema present, the description need not explain return structure, and the enumerated fields are a helpful preview rather than a substitute. For a no-param read tool this is nearly complete; only the hub-vs-summary distinction is left implicit.

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; baseline 4 applies. The field list in parentheses describes the response rather than inputs, adding no parameter meaning because none is needed.

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?

Names a specific verb (get) and resource (SprutHub controller info) and enumerates the returned fields (name, model, firmware, online status). It is distinguishable from device-level siblings like sprut_get_device, though it does not clarify its boundary against sprut_get_summary, which likely overlaps.

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 when-to-use guidance, no conditions, and no reference to alternatives such as sprut_get_summary. The agent is left to infer that this is the hub-level status lookup rather than the aggregate summary.

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