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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_approval_channels

Read-only

Retrieve approval channels filtered by status, environment, or profile ID, with paginated results. Use it to find the correct channel for routing human approval requests.

Instructions

List approval channels with optional filters. Returns paginated results.

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.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
limitNoItems per page
statusNoFilter by status: pending, active or archived
profile_idNoOnly this sub-account's configs (24 hex characters)
environmentNoFilter by environment (production or test)

Output Schema

NameRequiredDescriptionDefault
dataYes
limitsYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint is already supplied, so the safety profile is covered. The description goes beyond annotations by disclosing that results are paginated and by spelling out the authentication prerequisite and the surprising fact that start_login does not authorize this tool — genuinely non-obvious behavioral detail an agent would otherwise discover only by failing.

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?

Purpose is front-loaded in the first sentence and the access caveat is isolated in its own block, so an agent can stop reading after line one when credentials are already configured. The capitalized ACCESS section is slightly heavy-handed but each sentence carries actionable information.

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?

For a read-only paginated list tool with an output schema, full parameter descriptions and two enum filters, the description covers purpose, result shape, and the authentication gotcha. Nothing essential is missing; only the sibling-routing guidance is absent.

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 enums and regex patterns already documented for page, limit, status, profile_id and environment, so the schema carries parameter meaning. The description only gestures at 'optional filters' without adding filter semantics beyond the schema, making the baseline 3 correct.

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 opens with a specific verb and resource — 'List approval channels with optional filters' — plus the shape of the result ('paginated'). It does not explicitly differentiate itself from the single-resource sibling get_approval_channel, but the plural 'list' and the filter language make the intent clear enough to select it.

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?

The mention of 'optional filters' implies the tool is for browsing/filtering, and the ACCESS block gives a real prerequisite (a Proof account with PROOF_API_KEY set, and that start_login will not unlock this tool). However, it never states when to prefer this over list_circle_member_channels or when to switch to get_approval_channel for a single record.

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