Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

remove_circle_member_channel

Destructive

Remove a channel from a Circle member. Removing the last channel is allowed (the member simply becomes unreachable).

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

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": {
      "id": "<id>",
      "member_id": "<member_id>",
      "channel_id": "<channel_id>"
    },
    "name": "remove_circle_member_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCircle ID
member_idYesMember ID
channel_idYesChannel ID to remove

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real value on top: it discloses the non-obvious outcome of removing the final channel and spells out an authentication prerequisite that start_login does not satisfy. It does not describe the response or any confirmation/irreversibility behavior, keeping it short of a 5.

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?

Purpose is front-loaded in the first clause, the edge case follows immediately, and the access/auth block is clearly separated. Every sentence carries information an agent would otherwise have to discover at failure time.

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 destructive three-parameter mutation with an output schema present, the description covers the consequence of the action and the auth path, so return-value explanation is correctly omitted. It lacks any note on whether removal is reversible or how to discover channel IDs, a minor gap.

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 all three IDs (Circle, Member, Channel) documented and pattern-constrained, so the schema does the heavy lifting. The description adds no syntax or relationship detail about how id, member_id and channel_id interact, which is the baseline 3 case.

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?

States a specific verb ('Remove') against specific resources ('a channel from a Circle member'), which cleanly inverts the sibling add_circle_member_channel. An agent can distinguish it from add_circle_member_channel and remove_circle_member by verb alone, though the description never explicitly names those alternatives.

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 sentence 'Removing the last channel is allowed (the member simply becomes unreachable)' gives a useful guideline for a case an agent might otherwise avoid. However, there is no explicit routing to or away from siblings such as list_circle_member_channels (to find the channel_id) or remove_circle_member, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Proof Holdings toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources