Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BINNER_BASE_URLNoBase URL of local Binner instancehttp://localhost:8090
BINNER_LOG_FILENoOptional path to write log output in addition to stderr. CLI flag: --log-file
BINNER_MCP_HOSTNoBind address for HTTP / SSE transport. CLI flag: --host127.0.0.1
BINNER_MCP_PORTNoPort for HTTP / SSE transport. CLI flag: --port8000
BINNER_PASSWORDNoPassword for Binner authenticationadmin
BINNER_USERNAMENoUsername for Binner authenticationadmin
BINNER_LOG_LEVELNoLogging level (TRACE, DEBUG, INFO, WARNING, ERROR). CLI flag: --log-levelINFO
BINNER_MCP_CONFIGNoExplicit path to binnermcp_config.json. CLI flag: --config./binnermcp_config.json
BINNER_RETRY_COUNTNoMax retry attempts for transient network errors. CLI flag: --retry-count1
BINNER_RETRY_DELAYNoDelay in seconds between transient retry attempts. CLI flag: --retry-delay3.0
BINNER_MCP_TRANSPORTNoMCP transport (stdio, http, or sse). CLI flag: --transportstdio
BINNER_CATEGORY_DELIMITERNoDelimiter for category hierarchy paths. CLI flag: --category-delimiter::

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_system_statusA

Get Binner instance health, version, user identity, and inventory summary.

Args: check_cloud: Probe Binner Swarm cloud reachability.

list_partsB

Search and filter parts. Returns (id, part_number) unless extra fields are requested.

Args: query: Search keyword across part numbers and descriptions. part_type: Filter by category name or path. bin_number: Filter by storage bin. location: Filter by room or cabinet. package_type: Filter by footprint/package (e.g. '0805', 'SOIC-8'). manufacturer: Filter by manufacturer name. low_stock_only: Return only parts at or below threshold. fields: Extra fields to return (e.g. ['quantity', 'location', 'bin_number']). page: Page number (1-based). limit: Max results per page (1-500). sort_by: Column to sort by (default 'DateCreatedUtc'). direction: 'Ascending' or 'Descending'.

get_partsC

Get component details, bin locations, category paths, and datasheets by part number or ID.

Args: part_numbers: Part numbers to fetch. part_ids: Numeric part IDs to fetch. fields: Optional list of specific fields to return (e.g. ['quantity', 'bin_number', 'location']).

save_partsB

Batch create or update parts. Each item requires 'part_number'.

Args: parts: Part records with fields (e.g. 'part_number', 'quantity', 'cost', 'bin_number', 'part_type'). 'part_type' accepts a numeric ID (e.g. 10 or '10') or a category path/name string.

delete_partsC

Batch delete parts by part number or ID.

Args: part_numbers: Part numbers to delete. part_ids: Numeric part IDs to delete.

list_projectsA

Search and list maker projects with pagination, keyword search, and metadata.

Args: page: Page number (1-based). limit: Max projects to return (1-500). sort_by: Column to sort by (default 'DateCreatedUtc'). direction: 'Ascending' or 'Descending'. query: Optional search keyword to filter projects by name or description.

get_projectsB

Batch inspect maker projects by IDs or names, with optional BOM inclusion.

Args: project_ids: Numeric project IDs to inspect. names: Project names to inspect. include_bom: Include Bill of Materials for each project.

save_projectsB

Batch create or update maker projects. Each item requires 'name' (for create) or 'project_id' (for update).

Args: projects: Project records with 'name', optional 'description', optional 'project_id', optional 'archived'.

delete_projectsC

Batch delete maker projects by ID or name.

Args: project_ids: Numeric project IDs to delete. names: Project names to delete.

consume_project_bomC

Deduct inventory stock for assembling board units of a maker project's BOM.

Args: project_id: Numeric project ID to consume for. name: Project name to consume for. build_quantity: Number of complete board units to assemble (>= 1).

list_part_typesA

List part types structured as a lightweight hierarchical tree focusing on IDs and names.

Args: depth: Optional maximum depth of tree recursion (e.g. 1 for top-level root categories only). root_id: Optional root category ID to scope the tree to a single subtree. root_name: Optional root category name to scope the tree to a single subtree. include_descriptions: If True, includes description per node (default False). include_part_counts: If True, includes parts count per part type (default False).

save_part_typesC

Batch create or update part types.

Args: part_types: Part type records with 'name', optional 'description', optional 'parent_part_type_id', optional 'part_type_id'.

delete_part_typesC

Batch delete part types by ID or name.

Args: part_type_ids: Numeric part type IDs to delete. names: Part type names to delete.

manage_bom_partsC

Batch allocate, update, or remove BOM line items for a project.

Args: project_id: Target project ID. parts: BOM items with 'part_number'/'part_id', 'quantity', 'reference_designator', optional 'remove'.

lookup_cloud_partsB

Lookup manufacturer pinouts, package footprints, and datasheets from Binner Swarm cloud.

Args: part_numbers: Part numbers / MPNs to look up.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_status_resourceSystem health, version, auth identity, and aggregate inventory summary.
get_categories_resourceHierarchical category tree with category paths.
get_low_stock_resourceParts at or below low-stock threshold.

TDQS

B3.4/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have clearly distinct purposes: parts, projects, part types, BOM operations, cloud lookup, and system status are largely separate concerns. The main potential confusion is between list_parts (search by keyword/filter) and get_parts (fetch by ID/number), and between manage_bom_parts and consume_project_bom, but the descriptions draw workable boundaries.

Naming Consistency5/5

All names follow a consistent verb_noun snake_case pattern (list_parts, get_parts, save_parts, delete_parts, list_projects, save_part_types, etc.). The upsert verb 'save' is applied uniformly, and resource suffixes are consistent across the parts/projects/part_types families.

Tool Count5/5

15 tools is well-scoped for a parts/inventory management server spanning parts, projects, part types, BOM, and cloud lookup. Each family (parts, projects, part types) has a coherent CRUD-style cluster with no redundant or filler tools.

Completeness4/5

Parts and projects have full list/get/save/delete coverage, and BOM plus cloud lookup round out the lifecycle. Minor gaps: part types lack a dedicated get (though list_part_types can scope a subtree), and there is no direct tool for managing bins/locations despite parts referencing them.

Maintenance

ActivityMaintained
ResponsivenessNo issues