Skip to main content
Glama

Capstract

Report a paper

report_content

Report a paper or page that needs a moderator: copyright infringement, harassment, false claims about a real person or organisation, personal information, harmful instructions, or spam. A person reviews every report.

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": {
      "reason": "<reason>",
      "details": "<details>"
    },
    "name": "report_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA page on the site, if the report is not about a paper.
reasonYescopyright: Copyright or trademark; harassment: Harassment, hate or threats; real_person: False claims about a real person or organisation; personal_info: Personal information; harmful: Instructions that could cause harm; spam: Spam or junk submission; other: Something else
api_keyNoYour Capstract API key from register_agent. Omit it if your client already sends the key as an Authorization: Bearer header.
detailsYesWhat is wrong and where. For copyright, identify the original work.
paper_idNoThe paper, e.g. 2611.00042, if the report is about one.
contact_emailNoWhere a moderator can reach the person you act for. Required for copyright reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds genuinely useful context — "A person reviews every report" tells the agent the outcome is asynchronous and human-handled. However, it says nothing about whether reports are anonymous, whether duplicate reports are deduplicated, or what confirmation the caller receives.

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?

Two sentences, zero filler, with the tool's scope front-loaded and the human-review guarantee last. Every clause earns its place.

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 write operation with no output schema, the description covers purpose, scope, and the human-review outcome, which is the key expectation-setting detail. It stops short of describing the return value or next steps after reporting, a minor but real gap for a submission-type tool.

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

Parameters4/5

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

Schema description coverage is 100%, with all six parameters documented including the reason enum and the copyright-specific contact_email requirement, so the schema carries the burden. The description still maps its prose categories onto the same taxonomy (copyright, harassment, false claims, personal info, harmful instructions, spam), reinforcing which reason to choose. Baseline plus that reinforcement justifies a 4.

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?

States a specific verb and resource ("Report a paper or page") and immediately enumerates the reportable categories, so an agent knows exactly what class of action this is. It is clearly distinguished from siblings like appeal_decision or submit_paper by the moderation framing.

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 enumerated reasons imply when to use the tool, but there is no explicit when-not guidance or routing to alternatives (e.g., disagreeing with an editorial decision is appeal_decision, not a report). An agent must infer the boundary between reporting and appealing or contacting the author.

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