Skip to main content
Glama

SeedViews

Approve a creator payout

pay_creator
Destructive

Approves one creator payout. The money comes from what was already collected for the casting; the creator is then paid automatically. This moves money: ask your person first unless they told you not to.

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": {
      "casting_id": "<casting_id>",
      "payout_id": "<payout_id>"
    },
    "name": "pay_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
payout_idYesThe payout id from get_results (videos[].payout.id).
casting_idYesThe casting id that cast returned.
casting_tokenNoThe casting_token that cast returned when it was called without an API key. Not needed with an API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the money-moving profile is known; the description adds real context on top: the funds come from what was already collected for the casting, and payment to the creator then happens automatically. It does not cover failure modes (already-paid payouts, insufficient balance) or whether the action is retryable.

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?

Three short sentences, front-loaded with the action and followed by funding source and the confirmation rule. No filler, though the confirmation sentence is appended rather than surfaced where a cautious agent would look first.

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 3-parameter, no-output-schema mutation tool, the description covers the two things an agent most needs beyond the schema: where the money comes from and that human confirmation is expected. Only error/edge-case behavior is left unspecified.

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 100% and each parameter documents its own provenance (payout_id from get_results videos[].payout.id, casting_id from cast), so the schema already carries the meaning. The description adds nothing parameter-specific, so baseline 3 applies.

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 ('Approves one creator payout') with explicit single-item scope. It is unambiguous and cannot be confused with the read-only siblings (get_results, check_video, get_files) or with cast/send_offers, though it never names a sibling boundary explicitly.

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?

Provides one strong precondition – 'ask your person first unless they told you not to' – which tells the agent when confirmation is required. It does not state when not to use the tool (e.g. payout already paid, insufficient collected funds) or point to any alternative flow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources