Skip to main content
Glama

Physical Capability Cloud

by network.capability
OverviewDiscussionsAdmin

pcc_trilobio_build_config

Generate a complete KERNEL_CONFIG JSON for a Trilobio (tcode-api) fleet controller. Wraps buildTrilobioConfig() from the @pcc/trilobio npm package. Returns a TrilobioKernelConfig with sensible defaults (pollIntervalMs=3000, maxScriptTimeoutSec=3600, allowArbitraryScripts=false). The result can be passed to pcc-node start via the KERNEL_CONFIG env var, or handed to setup_generate_config / setup_register_device for direct API-driven registration. Note: this is a TypeScript package helper (no HTTP call). For programmatic use, import { buildTrilobioConfig } from "@pcc/trilobio".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFleet-controller URL on the LAN (host[:port], no trailing slash, no path) — e.g. http://192.168.1.50
apiKeyNoTrilobio fleet-controller API key (from the trilobot admin UI). Either apiKey OR username+password is required unless mockMode=true.
deviceIdNoLogical device ID within the kernel (default: trilobio-fleet-01)
kernelIdNoKernel ID this device belongs to (auto-generated as kernel_trilobio_<timestamp> if omitted)
mockModeNoBypass real HTTP and simulate runs. Use for CI / floor demos. Default: false.
passwordNoFleet-controller account password (basic-auth mode only)
usernameNoFleet-controller account username (basic-auth mode only)
pollIntervalMsNoPoll interval in ms for run status (range 500-60000). Default: 3000.
tcodeApiVersionNoPinned tcode-api version on the fleet controller. Format: 'latest' or semver (e.g. 1.25.1). Default: latest. Surfaces in evidence bundles for reproducibility.
mockRunDurationMsNoMock-mode simulated run duration in ms. Default: 2000.
maxScriptTimeoutSecNoMaximum allowed wall-clock seconds for a single tcode script (range 30-86400). Default: 3600.
allowArbitraryScriptsNoPermit customer-supplied tcode-api Python scripts (true) or only curated protocol IDs (false). Default: false. Set true only for trusted-counterparty deployments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint=false and destructiveHint=false already set, the description adds meaningful behavioral context beyond the annotations: it is a pure TypeScript package helper that makes no HTTP call, and it discloses the default values it emits (pollIntervalMs, maxScriptTimeoutSec, allowArbitraryScripts). That goes beyond what the annotations convey.

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?

Front-loaded with the purpose in the first sentence, followed by return shape, downstream usage, and the programmatic-import note. The import snippet is slightly gratuitous but not wasteful overall.

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?

No output schema exists, and the description compensates by describing the returned TrilobioKernelConfig and its defaults. It also covers the auth alternatives and mock mode via the schema. Complete enough for an agent to call it correctly, with only minor room to state when to prefer it over setup_generate_config.

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 description coverage is 100%, so each parameter including required-vs-optional auth rules and defaults is already documented in the schema. The description restates a few defaults but adds no syntax or format detail the schema lacks. Baseline 3 applies.

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?

States a specific verb and resource: 'Generate a complete KERNEL_CONFIG JSON for a Trilobio (tcode-api) fleet controller', and names the underlying function buildTrilobioConfig(). This clearly distinguishes it from siblings like pcc_trilobio_validate_options and pcc_trilobio_validate_script, which validate rather than build.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains downstream usage precisely: pass the result to `pcc-node start` via KERNEL_CONFIG, or hand it to setup_generate_config / setup_register_device. It also clarifies this is a package helper with no HTTP call. It lacks an explicit 'use this when...' vs alternative construct, but the surrounding context makes intent clear.

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

All Physical Capability Cloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources