Skip to main content
Glama
Sign In

Paxmod

by com.paxmod
OverviewDiscussionsAdmin

Get a player's flag history

get_player_history
Read-only

Returns one player's flagged messages in a project, newest first (up to 50), with a count by reason. Use the player id the game or app sends as user_id. Not available for organizations that keep player data in a separate region unless Paxmod has enabled it.

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": {
      "project_id": "<project_id>",
      "user_id": "<user_id>"
    },
    "name": "get_player_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many messages, 1 to 50. Default 50.
user_idYesThe player's id (exact).
project_idYesThe project's id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so well: it discloses result ordering, a hard 50-item cap, the aggregate count by reason, and an availability limitation for region-segregated organizations. It does not say what happens for a player with no flags, but the core behavioral picture is present.

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?

Three sentences, front-loaded with the return shape before any constraints, with no filler. The regional-availability sentence is slightly convoluted ('unless Paxmod has enabled it') but still carries a real constraint worth including.

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, the description must convey the return shape and does — newest-first list plus a count by reason — and it also flags the regional-data exception. The only gaps are edge-case behavior for players with no flags and whether results are ever truncated below the cap.

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 all three parameters are already documented, including the 1–50 limit and the exact-match user_id. The description adds modest value by explaining that user_id should be the id the game or app sends, but says nothing new about project_id or limit beyond the schema, so the baseline applies.

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?

States a specific verb and resource — returns one player's flagged messages within a project — plus ordering (newest first), a cap (up to 50) and a reason-count summary. The per-player scoping implicitly separates it from the project-wide sibling list_flagged_messages, but that sibling is never named, so the differentiation is left to inference.

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?

There is some guidance: 'Use the player id the game or app sends as user_id' tells the agent where the identifier comes from, and the regional-data sentence gives an availability caveat. However, there is no explicit statement of when to pick this tool over list_flagged_messages, and no prerequisites beyond the regional note.

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