Skip to main content
Glama

CarlNotes

Report something

report_content

Report something on CarlNotes to its admins: a topic, profile, team, team chat message, tasting note, note comment, finding, podcast episode, hot take, topic image, or Open Mic post's image, whose kind is topicPostImage. The report goes to the same queue as a report from the site, under the same daily limit, and can block the author too. Use it when the user asks Carl or CarlNotes to report this, flag this, or report this person.

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": {
      "subject_kind": "<subject_kind>",
      "subject_id": "<subject_id>"
    },
    "name": "report_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhat is wrong, in the user's words.
subject_idYesThe id of what is reported.
subject_kindYesWhat is reported. An Open Mic post's image is a topicPostImage.
should_block_authorNoWhether to block the author too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context beyond the annotations: the report lands in the same moderation queue as a site-originated report, is subject to the same daily limit, and may additionally block the author. That rate-limit and side-effect disclosure is valuable. It stops short of covering what happens on duplicate reports (relevant given idempotentHint=false), required permissions, or whether blocking is reversible.

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?

Purpose and usage trigger are front-loaded, which is good, but the middle sentence is a long comma-separated enumeration that duplicates the subject_kind enum and ends with an awkward trailing clause ('whose kind is topicPostImage') that is easy to misparse. The same ground could be covered in fewer, cleaner sentences.

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 non-idempotent moderation/flagging tool with no output schema, the definition supplies the essential decision inputs: what can be reported, what the user must say to trigger it, and the queue/limit/block side effects. It leaves minor gaps on optionality of 'reason' and duplicate-report behavior, but nothing critical for correct invocation 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%, so all four parameters are already documented, including the enum with its topicPostImage clarification. The description's prose enumeration mirrors the enum rather than adding new meaning, so the baseline 3 applies.

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 leads with a specific verb and resource ('Report something on CarlNotes to its admins') and enumerates the reportable subject types, so the agent knows exactly what this tool operates on. It partially distinguishes itself from the nearby block_user sibling by noting it 'can block the author too', though it never names that sibling or clarifies the boundary between reporting and blocking.

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?

Explicit invocation triggers are given: 'Use it when the user asks Carl or CarlNotes to report this, flag this, or report this person.' That is a clear positive condition with concrete user phrasing, but there are no exclusions or named alternatives (e.g., when to use block_user instead), which keeps it below a 5.

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.