Skip to main content
Glama
serial-hub-mcp

serial-hub-mcp

by yhuan416

service_info

Retrieve service name, version, endpoint, and optional changelog to confirm the deployed version and integration details.

Instructions

返回服务信息:服务名/版本/端点/(可选)变更摘要(changelog),用于确认部署版本与接入方式。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden; '返回' implies a read-only operation and the enumerated fields disclose what comes back, including that the changelog is optional. It says nothing about auth, caching, or whether the changelog is truncated, but for a zero-parameter read of static metadata the residual risk is low.

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 sentence, front-loaded with the returned fields and closing with the use case. The English gloss on changelog is the only redundancy and costs nothing.

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?

There is no output schema, so the description must describe return values, and it does — four fields with one flagged optional. Combined with zero parameters and no destructive behavior, this is sufficient for an agent to call it correctly; only the changelog's scope/format is left unspecified.

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 no parameters, so there is no parameter semantics to explain; the schema is trivially complete. Baseline 4 applies.

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 names a specific verb (返回) and resource (服务信息) and enumerates the returned fields — service name, version, endpoint, optional changelog — so an agent can tell this is deployment-metadata retrieval rather than, say, log_stats or get_status. It stops short of explicitly contrasting itself with the closest sibling, get_status, which keeps it from a 5.

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?

It supplies a use case ('确认部署版本与接入方式'), which implies when to call it, but there is no explicit when-not guidance and no named alternative for adjacent needs. Usage is inferable rather than stated.

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