Skip to main content
Glama
Sign In
Sealbridge

Sealbridge

by sealbridge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List local connections

acp_list_connections
Read-onlyIdempotent

Read local connection metadata for a signer DID without creating an identity or contacting peers, then inspect existing connections before a separate human CLI decision.

Instructions

Read local connection metadata for this server signer DID without creating an identity or contacting peers. Decisions require a separate human CLI action. No content or invitation material is returned. Empty arguments only; invalid arguments return JSON-RPC -32602.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesNumber of connection records.
connectionsYesLocal peer states and lifecycle metadata, including optional peerDisplayName from a verified card. Names are informational; DIDs determine identity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, closed-world, idempotent, and non-destructive behavior. The description adds useful context beyond that: it does not create an identity, does not contact peers, returns no content or invitation material, and rejects invalid arguments with JSON-RPC -32602.

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?

The description is short, front-loaded with the operation and scope, and each sentence carries a concrete constraint. There is no redundant or vague wording.

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 zero-parameter, read-only listing tool with full annotations and an output schema, the description is complete enough to call correctly. It covers scope, side-effect boundaries, argument behavior, and the human-decision caveat.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description reinforces this with 'Empty arguments only' and documents the invalid-argument error behavior, which adds minor value beyond the schema.

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 states a specific verb and resource: read local connection metadata for this server signer DID. It also scopes the result by saying no content or invitation material is returned. It does not explicitly name a sibling tool, so it is clear but misses full sibling differentiation.

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?

Usage is implied by the read-only local metadata framing, and the description warns that decisions require a separate human CLI action. However, it does not explicitly say when to use this tool instead of siblings such as acp_list_connection_requests or acp_list_invites.

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