concordance

report

[CHECK · internal] Report a community item (group_contribution, mesh_message, door_note) to the moderation floor. One report is a claim, never a verdict; at three DISTINCT reporters the item is held for a HUMAN steward's review (Deut 19:15). The counter never judges — it decides when a person must look. A report must be SIGNED (call moderation_signable first): three witnesses means three keys, never three invented names.

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": {
      "kind": "<kind>",
      "target_id": "<target_id>",
      "reason": "<reason>",
      "fields": "<fields>",
      "signature": "<signature>"
    },
    "name": "report"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`note`	No
`fields`	Yes	the exact fields from moderation_signable
`reason`	Yes
`signature`	Yes	detached signature over those bytes
`target_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedAug 4, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / fields / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / kind / maxLength
```
Added value: +4000
```
- addedInput schema / properties / note / maxLength
```
Added value: +4000
```
- addedInput schema / properties / reason / maxLength
```
Added value: +4000
```
- addedInput schema / properties / signature / maxLength
```
Added value: +4000
```
- addedInput schema / properties / target_id / maxLength
```
Added value: +4000
```

Changed4 schema fields changedJul 29, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "the exact fields from moderation_signable",
+  "type": "object"
+}

removedInput schema / properties / reporter

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / signature

Added value: +{
+  "description": "detached signature over those bytes",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "kind",
-  "target_id",
-  "reason",
-  "reporter"
-]New value: +[
+  "kind",
+  "target_id",
+  "reason",
+  "fields",
+  "signature"
+]

AddedJul 28, 2026

TDQS

A3.8/5.0

Behavior4/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 well: it discloses the sign-and-threshold workflow, the signature requirement, and the consequence (held for steward review). It omits return format, rate limits, and what happens below the threshold, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and efficient, but subsequent sentences mix useful operational detail with theological framing ('Deut 19:15', 'counter never judges'). The scripture reference and aphorisms dilute conciseness without adding actionable information.

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?

For a mutation tool with six parameters, no annotations, and no output schema, the description covers the critical workflow and prerequisites well. It still leaves parameter gaps and does not describe the response, but the core behavior an agent needs is present.

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 description coverage is only 33%. The description mentions 'kind', 'fields', 'signature', and the prerequisite for obtaining fields, which adds some meaning. But it does not explain 'target_id', 'reason', or the 'note' parameter, leaving half the semantics undocumented.

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 states a specific verb and resource: 'Report a community item (group_contribution, mesh_message, door_note) to the moderation floor.' It enumerates the acceptable item kinds, which distinguishes it from siblings like mesh_post or group_contribute. It does not, however, contrast itself with any specific sibling by name.

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?

Clear context for use, including the threshold behavior ('at three DISTINCT reporters the item is held for a HUMAN steward's review') and a prerequisite ('call moderation_signable first'). It does not explicitly state when NOT to use it or name alternative tools, keeping it from a 5.

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

All concordance tools Inspect

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.