Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_circle_member_channels

Read-only

Retrieve channel metadata for a Circle member, including channel, status, and verification time, without exposing identifiers. Use it to inspect a member's channel status and verification details.

Instructions

List a Circle member's channels. Returns channel metadata only (channel, status, verified_at) — an identifier is NEVER returned (SEC-PM-006).

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

NameRequiredDescriptionDefault
idYesCircle ID
member_idYesMember ID

Output Schema

NameRequiredDescriptionDefault
channelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "channels": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint=true annotation is consistent with the read-only listing behavior. Beyond annotations, it discloses the exact return shape (channel, status, verified_at) and a hard security constraint that no identifier is ever returned (SEC-PM-006), plus the account/API-key prerequisite, which is genuinely useful context.

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?

Two tight sentences lead with the action, then layer the return contract and access requirement. The access sentence is slightly verbose ('call this tool again') but nothing is wasted.

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?

With an output schema present, return values need not be enumerated, yet the description still summarizes them; auth prerequisites and the security constraint round it out. Only the relationship to sibling member/channel tools is left unstated.

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% with both parameters ('id' = Circle ID, 'member_id' = Member ID) documented, so the baseline is 3. The description adds no further meaning such as ID formats or whether the member must belong to the circle.

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 first sentence states a specific verb and resource ('List a Circle member's channels'), which is unambiguous on its own. It never names a sibling (e.g., list_circle_members or remove_circle_member_channel) to contrast with, so it falls short of a 5.

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?

It explains prerequisites for access (needs a Proof account, set PROOF_API_KEY, restart the server) and rules out one path ('start_login does NOT open this tool'). However, it gives no when-to-use guidance versus alternatives such as list_circle_members, so usage is only partly covered.

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