bizprint-mcp-server

get_station

Read-only

Retrieve detailed information about a specific print station by providing its ID, including title, status, version, domain, and assigned printers.

Instructions

Get details for a specific print station by ID. Returns station configuration including title, status, version, domain, and assigned printers.

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": {
      "stationId": "<stationId>"
    },
    "name": "get_station"
  }
}

Input Schema

Name	Required	Description	Default
`stationId`	Yes	The station ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to reiterate non-destructiveness. The description adds value by listing returned fields (title, status, version, domain, assigned printers), but it omits behavior such as error responses when stationId is invalid or whether partial data can be returned. With annotations already covering safety, a 3 is appropriate.

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 two concise sentences with zero wasted words. It front-loads the purpose and then lists what is returned. Every sentence adds value.

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?

Given the tool's simplicity (one parameter, no nested objects, no output schema), the description is nearly complete. It explains what the tool returns, but could mention that the ID must correspond to an existing station and that it returns a single object. Still, it's sufficient for an agent to understand the tool's behavior.

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?

Input schema covers 100% of parameters, with stationId described as 'The station ID' and a minimum constraint. The description adds context that the ID is used to get station details, but does not add meaning beyond the schema. Baseline 3 is correct.

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 clearly states it gets details for a specific print station by ID, listing exactly what configuration fields are returned (title, status, version, domain, assigned printers). This verb+resource structure is specific and distinguishes it from sibling tools like list_stations (which lists many) and get_printer (which retrieves a different resource).

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?

The description implies usage when you need details for a specific station by ID, which is standard for a get-by-ID tool. However, it provides no guidance on when to use alternatives like list_stations or get_printer, nor does it mention prerequisites such as the station needing to exist.

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

Deploy Server