Skip to main content
Glama
agent-context-bridge

agent-context-bridge

acb_status

Read-onlyIdempotent

Check workspace initialization and shared context store health in read-only mode. Returns record counts, store size, targets, and version so you can verify wiring before search or inject.

Instructions

Read-only workspace diagnostic for the shared context store. Returns {initialized, records, store_bytes, last_updated, targets, version}. Never creates the store; uninitialized workspace returns initialized:false. Use to verify ACB wiring/health before search/inject.

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

Input Schema

NameRequiredDescriptionDefault
dirNoOptional workspace path confined under the server --dir root; outside root rejected (-32602). Default: server cwd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive semantics, and the description goes beyond them by guaranteeing it never creates the store and by specifying the uninitialized-workspace return value (initialized:false). It also enumerates the returned fields, which substitutes for the absent output schema; error/auth behavior is not covered.

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?

Three tight sentences: purpose and safety first, return payload second, usage routing last. No redundant restatement of the tool name or filler.

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

Completeness5/5

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

For a one-optional-parameter diagnostic with no output schema, the description supplies the return fields, the uninitialized case, and the side-effect guarantee. An agent has everything needed to call it and interpret the result.

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 coverage is 100% — the single optional 'dir' parameter already documents the root confinement and the -32602 rejection. The description adds no syntax or format detail beyond the schema, so 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?

The description opens with a specific verb+resource ('Read-only workspace diagnostic for the shared context store') and immediately states the return shape. It separates itself from acb_search by framing itself as a pre-flight check ('before search/inject') rather than a data-retrieval tool.

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?

It gives clear context for use ('verify ACB wiring/health before search/inject'), which tells the agent to call this before the search sibling. It doesn't state explicit exclusions (e.g., 'do not use to retrieve records'), so it falls short of a full when/when-not pair.

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