Skip to main content
Glama
Sign In
Bambi A1 MCP

Bambi A1 MCP

by chandraaditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_printers

Read-only

Lists cloud-bound printers while omitting tokens and serial numbers, so you can identify available devices without exposing sensitive credentials.

Instructions

List cloud-bound printers without returning tokens or serials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds a genuine behavioral disclosure beyond them: returned records are redacted of tokens and serials. That tells an agent what it will and will not receive, which matters for follow-up calls.

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 zero filler; the redaction caveat is attached directly to the core action rather than buried in a separate clause. Nothing could be removed without losing information.

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 parameterless read-only listing with no output schema, the description covers the action and the key return-value property (no secrets) that an agent cannot see from structured fields. Pagination or ordering behavior is unaddressed, which is a minor gap for an inventory call.

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 no parameter semantics for the description to explain; the baseline for a parameterless tool applies. The schema is also fully closed with additionalProperties=false, leaving no ambiguity.

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?

States a specific verb and resource ("List cloud-bound printers") with a scoping qualifier that separates it from status-oriented siblings like printer_status. It stops short of naming a sibling it replaces, so an agent must infer the boundary rather than being told it.

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 intent to enumerate the printer inventory is implied by "List", and the contrast with printer_status is reasonably inferable, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives.

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