Skip to main content
Glama

report_to_police

Report another player to in-game police (confirm details with the user 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": {
      "report_target_user_id": "<report_target_user_id>"
    },
    "name": "report_to_police"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_noteNo
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
report_target_user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and does not disclose the consequences of filing a report — whether the target is notified, whether reports are permanent/irreversible, or whether permission or evidence is required. Only the confirm-with-user caution adds behavioral value; the side effects of this mutation remain opaque.

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?

A single compact sentence with the primary action front-loaded and the safety caution properly parenthesized. Efficient, though the brevity contributes to the behavioral and parameter gaps above.

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

Completeness2/5

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

A three-parameter mutation tool with no annotations, no output schema, and only one-third schema coverage needs substantially more description than one sentence. An agent still cannot tell what a successful report returns, whether the report is visible to the accused, or how to phrase the required note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — 'notification_message' is documented in the schema, but 'report_note' and 'report_target_user_id' are bare strings with no explanation anywhere. The description does not compensate: it never explains what a report note should contain or the expected format of the target user ID.

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 ('report') and resource ('another player to in-game police'), which is unambiguous on its own. No sibling tool performs reporting, so differentiation is implicit rather than stated, keeping it just 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?

The parenthetical 'confirm details with the user first' supplies a real precondition for invoking the tool. However, it offers no guidance on when reporting is appropriate versus, say, using send_dm or get_chat_with_player to resolve an issue, nor any exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources