Skip to main content
Glama
Sign In

VibeAdmin

by solutions.easy-admin
OverviewDiscussionsAdmin

Add or deduct credits

add_credits
Destructive

Add credits to a user's balance (use a negative number to deduct). Changes the numeric credits custom field in the user's source system. Confirm the amount with the person you are helping first.

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": {
      "user_id": "<user_id>",
      "amount": "<amount>"
    },
    "name": "add_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoName of the numeric custom field. Default: credits.
amountYesWhole number, non-zero, at most 1,000,000 either way.
user_idYesThe user's id in your app (preferred) or the VibeAdmin id from list_users.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine context beyond that: the write lands in the user's source system and only affects one numeric custom field, which bounds the blast radius. It stops short of saying whether writes are reversible or audited.

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

Conciseness5/5

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

Three short sentences, front-loaded with the operation and its inverse, then the mutation target, then the safety instruction. Nothing is repeated from the name or title and no sentence is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and with annotations covering destructiveness and the schema covering all three parameters, most of the burden is discharged. What is left unaddressed is the result of the call — whether it increments or overwrites the existing balance, and what happens when `field` does not exist — which matters for a destructive mutation.

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 100%, so the baseline is 3, but the description adds meaning the schema omits: the schema only says 'non-zero', while the description makes explicit that a negative value is the sanctioned way to deduct. It also implicitly frames `field` as a numeric custom field rather than an arbitrary property.

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 concrete verb and resource ('Add credits to a user's balance') and immediately defines the negative-amount inverse, so both directions of the operation are unambiguous. It also names the exact underlying object mutated ('the numeric `credits` custom field in the user's source system'), which no sibling tool touches.

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?

Provides a real precondition — 'Confirm the amount with the person you are helping first' — plus the practical rule that negatives deduct. It lacks any routing to alternatives, but no sibling tool overlaps this capability, so there is little to exclude against.

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

All VibeAdmin toolsInspect
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