Skip to main content
Glama

Read moderation decisions

heystack_read_moderation
Read-onlyIdempotent

Read public moderation decisions. The response does not include the reported content. Use this to see a decision or a page of decisions. Do not use it to report a document; a report is a signed heystack_submit_contribution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "heystack_read_moderation"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseNoOne moderation case id. Omit to list a page of decisions.
pageNoPage number, starting at 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a non-obvious payload fact — that the reported content is excluded from the response — which matters because there is no output schema. It stops short of describing what a decision record contains or how paging terminates.

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 short sentences, each earning its place: purpose, return caveat, then exclusion plus alternative. The scope statement and the routing warning are both front-loaded with no filler.

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 two-optional-parameter read tool with full schema coverage, the description covers purpose, exclusion, and the key response caveat. With no output schema, it could say slightly more about what a decision record returns, but nothing essential to calling it correctly is missing.

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 100%, and the 'case' parameter already documents 'Omit to list a page of decisions', so the baseline is 3. The phrase 'a decision or a page of decisions' reinforces the single-vs-list mode but adds little beyond what the schema states.

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 opens with a specific verb and resource ('Read public moderation decisions') and immediately clarifies scope: one decision or a page of decisions. It explicitly separates itself from the report-writing flow by naming heystack_submit_contribution, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives both a when-to-use ('see a decision or a page of decisions') and a when-not-to-use ('Do not use it to report a document'), and supplies the correct alternative by name. The routing decision an agent is most likely to get wrong is resolved in one sentence.

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