Skip to main content
Glama

Pure Report — Neutral News

by report.pure
OverviewDiscussionsAdmin

About & methodology

about_pure_report
Read-only

How Pure Report works — the bias scale, neutralization method, the two-gate verification for event accounts, lean labeling, coverage scope (topic list), and the support contact. Call this to cite the source or explain its methodology to a user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
article_idNoOptional context for the report.
event_slugNoOptional context for the report.
report_bodyNoOptional. The detail needed to act.
report_kindNoOptional, defaults to bug.
report_subjectNoOptional. Providing this (with report_body) files feedback and returns a ref under "filed" — use only if submit_feedback is missing from your tools.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
filedNo
supportYes
websiteNo
freshnessNo
bias_scaleYes
what_it_isNo
lean_labelingNo
coverage_scopeNo
neutralizationNo
verification_gateNo
reporting_problemsNo
reporting_problems_if_submit_feedback_is_missingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / report_kind / enum
      Previous value: -[
-  "data_error",
-  "bug",
-  "feature",
-  "question"
-]New value: +[
+  "bug",
+  "dx",
+  "data_error",
+  "data_gap",
+  "feature",
+  "question",
+  "other"
+]
  2. Changed8 schema fields changed
    • addedInput schema / properties / article_id
      Added value: +{
+  "description": "Optional context for the report.",
+  "type": "integer"
+}
    • addedInput schema / properties / event_slug
      Added value: +{
+  "description": "Optional context for the report.",
+  "type": "string"
+}
    • addedInput schema / properties / report_body
      Added value: +{
+  "description": "Optional. The detail needed to act.",
+  "type": "string"
+}
    • addedInput schema / properties / report_kind
      Added value: +{
+  "description": "Optional, defaults to bug.",
+  "enum": [
+    "data_error",
+    "bug",
+    "feature",
+    "question"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / report_subject
      Added value: +{
+  "description": "Optional. Providing this (with report_body) files feedback and returns a ref under \"filed\" — use only if submit_feedback is missing from your tools.",
+  "type": "string"
+}
    • addedOutput schema / properties / filed
      Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
    • addedOutput schema / properties / reporting_problems
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / reporting_problems_if_submit_feedback_is_missing
      Added value: +{
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bias_scale": {
+      "type": "string"
+    },
+    "coverage_scope": {
+      "type": "object"
+    },
+    "freshness": {
+      "type": "string"
+    },
+    "lean_labeling": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "neutralization": {
+      "type": "string"
+    },
+    "support": {
+      "type": "string"
+    },
+    "verification_gate": {
+      "type": "string"
+    },
+    "website": {
+      "type": "string"
+    },
+    "what_it_is": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "bias_scale",
+    "support"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

With annotations declaring readOnlyHint=true, the bar is lower, and the description adds useful context about the tool's informational content. However, it does not mention the potential write side effect when report_subject and report_body are provided (which files feedback), nor any other limitations. It provides moderate transparency beyond the annotation but not full behavioral disclosure.

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?

The description is two sentences, front-loaded with a clear list of content, and ends with a practical usage directive. Every word earns its place with no redundancy or fluff.

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?

The tool is an informational resource, and the description covers its full scope and purpose. Since an output schema exists, return format details are not required. The presence of optional parameters is not explained in the description, but they are well-documented in the schema, so the overall context is complete enough.

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%, so the baseline is 3. The description does not add any meaning to the parameters, but the schema descriptions are already detailed, especially for report_subject. No additional compensation is needed or provided.

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 clearly states what the tool does: it explains how Pure Report works, listing specific content areas (bias scale, neutralization method, verification, labeling, coverage, support contact) and explicitly says when to call it ('to cite the source or explain its methodology'). This distinguishes it from sibling tools like get_article or search_news.

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 provides direct usage guidance ('Call this to cite the source or explain its methodology to a user'), making the intended use clear. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to disambiguate from siblings. The schema additionally provides fallback guidance for report_subject, but that is outside the description.

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

All Pure Report — Neutral News 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