Skip to main content
Glama
Sign In
agentbus

agentbus

by onicarps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agentbus_lock_status

Check whether a resource is locked without acquiring it. Requires no authentication, enabling agents to verify coordination state directly.

Instructions

Check lock state without acquiring (no auth required).

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": {
      "resource": "<resource>"
    },
    "name": "agentbus_lock_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0
  2. Removedv0.16.3
  3. Addedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, description discloses an important behavioral trait ('no auth required'), but omits other aspects like idempotency, side effects, or what the lock state entails. Minimal but not misleading.

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?

Extremely concise with no filler. However, the brevity sacrifices clarity on parameter semantics. Front-loaded with key differentiating info.

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?

Despite low complexity and presence of output schema (not shown), the description fails to explain the sole required parameter. Leaves agent guessing about 'resource'.

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

Parameters1/5

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

Schema description coverage is 0% and description does not mention the 'resource' parameter at all. No guidance on its meaning, format, or constraints.

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?

Clearly states verb 'Check' and resource 'lock state', distinguishing it from sibling tools like lock_acquire, lock_release, and lock_renew. No ambiguity.

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?

Implicitly indicates when to use ('without acquiring') and notes no auth required, but does not explicitly list alternatives or when not to use. Context from sibling names helps, but description lacks explicit guidance.

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