Skip to main content
Glama
Sign In

Gemmein

by com.gemmein
OverviewDiscussionsAdmin

Give a test member credits

test_member_credits

Gives a test member credits in Development, at once with no approval — the same credits the dashboard gives, on their credit history with the note. Test members only (made with test_member_add); anyone else is refused, and it never reaches Live — Live's customers get credits through request_grant_credits, approved by the founder. amount is whole credits (1–100,000); note is one line saying why. A second call gives them again. On the founder's Logs.

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": {
      "as": "<as>",
      "amount": "<amount>",
      "note": "<note>"
    },
    "name": "test_member_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
asYesthe test member's name
noteYesone line saying why, up to 200 characters
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the grant needs no approval, that credits land on the member's credit history with the note, that a second call grants again (matching idempotentHint=false), and that the action shows in the founder's Logs. That is rich behavioral context the annotations alone don't provide.

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?

It is a single front-loaded passage with no wasted sentences; the safety/scope constraint precedes the parameter details. It is dense but every clause carries distinct information.

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

Completeness5/5

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

There is no output schema, yet the description explains the observable effects (credit history entry with note, Logs visibility) and the retry behavior. For a 3-parameter, non-destructive mutation, an agent has everything needed to call it correctly.

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% and the schema leaves 'amount' completely undocumented; the description fills that gap with unit and bounds ('whole credits (1–100,000)'). 'note' and 'as' get less added meaning beyond the schema's own descriptions, keeping this just short of a 5.

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?

The description opens with a specific verb and resource ('Gives a test member credits') and immediately bounds the scope to Development. It clearly separates this tool from request_grant_credits, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

It states explicitly when to use this tool (test members only, made with test_member_add), when not to (anyone else is refused), and the alternative for Live customers (request_grant_credits, founder-approved). Nothing about routing is left to inference.

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

All Gemmein toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources