LLM Bus

register

Declare your presence in a lane with an optional status message to coordinate ownership and liveness among AI agents.

Instructions

Announce your presence in a lane with an optional short status (who-owns-what + liveness).

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": {
      "lane": "<lane>"
    },
    "name": "register"
  }
}

Input Schema

Name	Required	Description	Default
`lane`	Yes
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions 'who-owns-what + liveness' but does not explain effects like overwriting previous registrations, timeout behavior, or authentication requirements. Critical behavioral details are missing.

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?

The description is a single, front-loaded sentence that efficiently conveys the core purpose. However, it is too concise given the need for more detail, especially with 0% schema coverage and no annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (two parameters, no output schema, no annotations) and sibling tools, the description is incomplete. It does not explain registration duration, liveness tracking, or how to deregister, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add meaning. It identifies 'lane' and 'status' but provides no specifics on valid values or format beyond a vague hint about ownership and liveness. The description fails to clarify parameter semantics adequately.

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 description clearly states the tool announces presence in a lane with an optional status, using specific verbs and resources. However, it does not differentiate from sibling tools like 'claim' or 'who_is_active', which may have overlapping functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'claim' for acquiring ownership or 'who_is_active' for checking presence. The description lacks any when-to-use or when-not-to instructions.

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