Skip to main content
Glama
Sign In

Paxmod

by com.paxmod
OverviewDiscussionsAdmin

Test word rules

test_word_rules
Read-only

Shows what a project's word rules do to each message: block (flag without checking), bypass (pass without checking), or scan with the text rewritten by remove and replace rules. Send draft rules to try changes before saving them. No model call, nothing stored, no credits used.

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": {
      "api_key": "<api_key>",
      "messages": "<messages>"
    },
    "name": "test_word_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesPaxmod API key for the project.
messagesYesMessages to test, up to 50.
word_rulesNoDraft rules. Leave out to test the saved ones. Whole words, case insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses that no model call occurs, nothing is persisted, and no credits are consumed — exactly the cost and side-effect context an agent needs before choosing a dry-run tool. It also explains the shape of the result (per-message block/bypass/rewritten text).

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 tight sentences, front-loaded with the core behavior and ending with the cost/side-effect guarantees. No filler and no repetition of schema fields.

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 states what the result conveys (blocked, bypassed, or scanned with rewritten text), plus cost and persistence guarantees. Nothing material is missing for correct invocation.

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; the description adds value by framing word_rules as a 'draft' that previews changes before saving and by tying the modes to observable outcomes. Minor mismatch: it says 'replace' rules while the enum uses 'substitute', which slightly blurs the mode mapping.

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 description names a specific verb and resource ('Shows what a project's word rules do to each message') and enumerates the three possible outcomes (block, bypass, scan-with-rewrite). It implicitly separates itself from siblings like moderate_text via 'No model call, nothing stored, no credits used', though it never names an alternative tool outright.

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?

'Send draft rules to try changes before saving them' gives a clear when-to-use condition, and the schema note about leaving rules out to test saved ones complements it. There is no explicit when-not guidance or named alternative (e.g. vs. moderate_text or test_policy), which keeps it short of a 5.

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