Hook Detector

set_team_member_cap

Set a member's monthly cap on the pool (null removes it). A run started near the cap holds only what is left, so the cap is never passed mid-run (403 team_cap_reached below a run's minimum or a tool's price). Owner only. Needs admin. Free. Same as PATCH /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>",
      "monthly_cap": "<monthly_cap>"
    },
    "name": "set_team_member_cap"
  }
}

Input Schema

Name	Required	Description
`api_key`	No
`member_id`	Yes	a member_id from get_team
`monthly_cap`	Yes	1 to 1,000,000 credits a UTC month, or null for no cap

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses authorization requirements (owner/admin), an error code (403 team_cap_reached) with its two trigger conditions, the mid-run partial-hold semantics, and that the call is free. It also maps to the REST endpoint for cross-reference.

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?

Dense but front-loaded: the core action and null behavior lead, with preconditions and edge cases following. The parenthetical about 403 causes is slightly compressed, but no sentence 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?

An output schema exists, so return values needn't be explained. For a mutation tool with no annotations, the description covers auth, failure modes, and mid-run semantics well; only the api_key parameter is left implicit.

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?

Schema coverage is 67%, with member_id and monthly_cap already documented. The description adds meaning beyond the schema by explaining that null removes the cap and how the cap interacts with an in-flight run (holds only what remains). The api_key parameter remains unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (set), resource (a member's monthly cap on the pool), and scope, with the null-removal variant stated immediately. An agent can distinguish this from move_team_credits or admin_adjust_credits without inspecting any schema.

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

Usage Guidelines4/5

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

Explicitly states 'Owner only. Needs admin.' and the 403 team_cap_reached condition, which tells the agent the prerequisite and failure mode. It doesn't name a sibling alternative for adjusting team credit allocation, but the context is clear enough to select correctly.

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?