Skip to main content
Glama
Sign In

Paxmod

by com.paxmod
OverviewDiscussionsAdmin

Create a Paxmod test API key

create_test_api_key

Creates a working text-moderation API key with no account: 100 messages over 72 hours, standard mode, every category on. Returns api_key and claim_url; opening claim_url keeps the key in a Paxmod account. Limited to 3 keys per address per day.

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": "create_test_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional project name, for example the game's name.
sourceNoOptional: the agent or tool asking, for example claude-code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the quota (100 messages over 72 hours), fixed mode and category configuration, both return fields, the semantics of claim_url, and an explicit rate limit (3 keys per address per day). This is precisely the behavioral context annotations cannot express.

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?

Two sentences, front-loaded with the action and constraint, then the return values, then the rate limit. Every clause carries distinct information (quota, config, outputs, claim semantics, throttling) with no restatement of the name or title.

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, and the description compensates by naming both returned fields and explaining what claim_url does. For a zero-required-parameter creation tool with no annotation detail on side effects, nothing an agent needs to call it or interpret the result is missing.

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%, so name and source are already documented by the schema with examples; the description adds nothing about them. That is acceptable given the schema's completeness, so the baseline of 3 applies, but the description could have noted that both are optional metadata only.

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?

The first clause states a specific verb and resource ('Creates a working text-moderation API key') and immediately qualifies the scope ('with no account'), which is the key distinguishing trait versus account-bound siblings. It does not name or contrast any sibling tool, so it stops short of a 5.

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 is only implied: an agent can infer this is the bootstrap path for trying moderation without an account. There is no explicit when-to-use/when-not statement and no alternative named (e.g., it never points to moderate_text or test_policy as the follow-up once a key exists).

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

All Paxmod 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