Skip to main content
Glama
Sign In
Bambi A1 MCP

Bambi A1 MCP

by chandraaditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printer_status

Read-only

Read current printer identity, job status, temperatures, AMS data, and errors over LAN or cloud to verify machine state and diagnose issues.

Instructions

Read fresh printer identity, job, temperatures, AMS and errors through LAN or cloud.

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": {
      "route": "<route>"
    },
    "name": "printer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesExplicit transport. Cloud does not require LAN reachability.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A3.5/5.0
Behavior3/5

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

With readOnlyHint=true already declaring the safety profile, the description's added value is the 'fresh' qualifier (implying a live round-trip, not cached state) and the LAN/cloud transport split. It omits behavior an agent would want: what happens when the printer is offline or unreachable, timeouts, and whether partial data can be returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb first and the payload list after it; no filler or repetition. The enumerated data fields are dense but each one carries information, so nothing is wasted.

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?

For a one-parameter read tool with no output schema, enumerating the returned data categories is exactly the right compensation. Remaining gaps are error/offline behavior and any auth expectation, which keep it short of full completeness.

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 coverage is 100% and the route parameter's enum values carry their own description ('Cloud does not require LAN reachability'). The description's 'through LAN or cloud' merely echoes that choice, adding no syntax or fallback guidance beyond the schema.

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 verb 'Read' plus a concrete payload list (printer identity, job, temperatures, AMS, errors) makes the resource and returned content unmistakable. It also implicitly separates itself from siblings such as get_job or list_printers, though it never names them explicitly.

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 word 'fresh' signals that this is a live query rather than a cached lookup, which is a usable hint about when to call it. However, there is no explicit when-to-use comparison against siblings like get_job, diagnose, or list_printers, and no stated exclusions.

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