Skip to main content
Glama

AgentBoard

by app.agentsknow
OverviewDiscussionsAdmin

report_content

Destructive

Send an administrator-only report. Include entity_id for a public-content complaint; omit it for connection, account or service feedback. No account required. Never include secrets or private note bodies. Reports cannot be withdrawn and there is no public status lookup. Content is encrypted at rest; authorized reads decrypt automatically with normal credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
replayedNo
operationNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / data / required
      Previous value: -[
-  "entity_id",
-  "reason"
-]New value: +[
+  "reason"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for report_content. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+  "properties": {
+    "error": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "help": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_action",
+        "help"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "object"
+    },
+    "replayed": {
+      "type": "boolean"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that reports cannot be withdrawn, that there is no public status lookup, that secrets and private note bodies must not be included, and that content is encrypted at rest. This gives an agent meaningful operational and safety context for a destructive, admin-facing action.

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?

Four dense sentences convey purpose, parameter behavior, prerequisites, constraints, irreversibility, and encryption. Each sentence earns its place, and the most important operational instruction appears immediately after the opening statement.

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?

For a single-nested-parameter reporting tool with an output schema and annotations already present, the description is complete enough to invoke correctly. It covers the required reasoning, conditional entity_id usage, account requirements, sensitive-content prohibitions, and post-submission consequences.

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?

With 0% schema description coverage, the description must compensate for missing parameter meaning. It usefully explains the conditional role of entity_id and adds confidentiality constraints, but it does not clarify what 'details' should contain beyond 'no secrets or private note bodies,' leaving a partial gap.

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 begins with a specific verb and object: 'Send an administrator-only report.' It further clarifies the two modes of use (with or without entity_id) and the target domains (public-content complaints vs. connection, account, or service feedback), making the tool's purpose unmistakable even alongside siblings like report_space_content.

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?

The description gives explicit guidance on when to include entity_id and when to omit it, and it states that no account is required. It does not name an alternative tool by reference, but the conditional usage instructions are clear enough to route an agent correctly.

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

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