Hook Detector

remove_team_member

The owner removes a member; anyone leaves with member_id "me". A removed member's next spend comes from their own balance, never the pool. The owner leaving with members is 409 team_has_members; alone it ends the team and returns the pool. Needs admin. Free. Same as DELETE /v1/team/members/{member_id}.

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": {
      "member_id": "<member_id>"
    },
    "name": "remove_team_member"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No
`member_id`	Yes	a member_id from get_team, or "me" to leave

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Since there are no annotations, the description carries the full burden and performs exceptionally well. It discloses complex behavioral traits not apparent from the name, such as how the removed member handles future spending ('comes from their own balance, never the pool') and how team state changes upon removal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely dense, front-loading highly technical operational rules that may not be immediately digestible. While every sentence adds necessary technical value, the structure leans heavily on technical jargon rather than clarity or ease of consumption.

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?

Given the complexity of team member removal, the definition is highly complete. It covers access requirements, behavioral outcomes, state transitions, and the self-removal option, leaving no critical functional gaps for the agent to resolve.

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

Parameters5/5

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

The schema coverage is low (50%), yet the description adds immense semantic depth by explaining the functionality of the critical 'member_id' parameter ('anyone leaves with member_id 'me'') and its profound effect on team structure and finances.

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 clearly states the action ('The owner removes a member'), the resource ('member'), and the context ('owner'). Although the description rapidly branches into complex state outcomes, the primary function remains unambiguously clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

This section provides excellent guidance by defining both operational prerequisites ('Needs admin. Free.') and critical conditional usage based on input: whether the owner leaves with other members or alone, and the resulting team state.

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

All Hook Detector tools Inspect

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

Need Help?