Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get account credits

get_account
Read-only

Check account credit status, including available balance, debt, held credits, and support replies, to see if a UGC video run can proceed or needs credits purchased.

Instructions

This account's credits. Free. debt_credits above zero refuses make_ugc (debt_outstanding) until credits are bought; else balance_credits is what a run can spend; holds_credits are held by runs in progress. support_replies holds our replies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.39.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observedv0.20.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish the safe-read profile, so the description's job is to add behavior, which it does: it explains the debt gate that blocks make_ugc, distinguishes spendable balance from in-flight holds, and notes that support_replies carries our replies. This is real operational context an agent would not get from readOnlyHint alone.

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?

Every sentence carries information, but the phrasing is telegraphic and fragmentary, chained with semicolons and an aside about support_replies tacked onto the end. The gating rule about debt_credits is the most important fact yet appears mid-sentence rather than front-loaded.

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?

With no output schema and no parameters, the description must carry the return-value meaning, and it names the four credit categories and their relationships. A little more on what "Free" implies (no quota charge) or on refresh/freshness would close the remaining gap.

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?

There are zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The clauses instead explain the semantics of the returned fields, which is a reasonable substitute.

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

Purpose3/5

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

The opening fragment "This account's credits" identifies the resource but never states a verb, and it reads as a label rather than a definition. The follow-up clauses do enumerate what the credits payload contains (debt_credits, balance_credits, holds_credits), which makes the subject concrete, but the agent has to infer that this is a read of the account's credit state.

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?

Usage context is implied rather than stated: "Free" signals no charge for calling it, and the note that debt_credits above zero refuses make_ugc tells an agent it is a prerequisite check before that sibling. There is no explicit "call this before/when" sentence and no mention of the other credit-adjacent siblings in the list.

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

Deploy Server

Other Tools