Hook Detector

move_team_credits

Move credits between your balance and the team's pool; 402 when the side giving holds less, and nothing moves. Owner only. Needs admin. Free. Same as POST /v1/team/credits.

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": {
      "credits": "<credits>",
      "direction": "<direction>"
    },
    "name": "move_team_credits"
  }
}

Input Schema

Name	Required	Description
`api_key`	No
`credits`	Yes	1 to 1,000,000
`direction`	Yes	"in": your balance to the pool; "out": the pool back to you

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/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 credibly: it discloses the failure mode (402 when the giving side is short), the atomicity guarantee ('nothing moves'), the permission model (owner only, needs admin), and the cost (free). Missing only idempotency/retry semantics, which keeps it off 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.

Conciseness4/5

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

Four short clauses, front-loaded with the action and followed by the failure mode, permissions, and cost. The telegraphic fragments are efficient rather than confusing; the trailing API-mapping note earns its place only for agents that reason in REST terms.

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 two-required-parameter mutation with an output schema (so return values need no explanation), the description covers permissions, failure behavior, and cost. The one real gap is the absence of disambiguation from sibling credit tools.

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 coverage is 67% and both business parameters are already documented in the schema, including the enum meanings for 'in'/'out' and the 1–1,000,000 range. The description's restatement of which side moves to which adds only marginal clarity beyond what the schema states.

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 and resource ('Move credits between your balance and the team's pool') with scope made explicit by the direction pair. It does not name or differentiate from the closest sibling, admin_adjust_credits, so an agent must infer which credit-movement tool applies.

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?

'Owner only. Needs admin.' gives real invocation prerequisites, which is more than most descriptions offer. But there is no guidance on when to choose this over admin_adjust_credits, balance, or usage — the sibling set contains several credit-related tools and none are addressed.

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?