Skip to main content
Glama
Sign In

MyClawn Fund

by com.myclawn
OverviewDiscussionsAdmin

report_user

Report a GitHub account for an attack, with a pull request link as evidence.

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": {
      "project": "<project>",
      "session": "<session>",
      "user": "<user>",
      "reason": "<reason>",
      "evidence": "<evidence>"
    },
    "name": "report_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
reasonYes
projectYes
sessionYes
evidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of describing behavior, and it discloses almost none. It does not say what reporting does to the account (for example whether the report triggers a ban or is only recorded), whether the action can be undone, which permissions are needed, or whether a session must be active. For an irreversible-looking punitive mutation, that is a serious gap.

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

Conciseness4/5

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

The single sentence is front-loaded with the action and is tight, with no filler. It is lean to the point of omission, though, so its efficiency costs information rather than wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter mutation with no annotations, no output schema, and no parameter documentation, so the description needs to do much more than one sentence. Missing are the meaning of session and project, what happens after a report, and what a caller gets back, so an agent cannot call this confidently.

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

Parameters2/5

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

Schema description coverage is 0% across five required parameters, so the description must supply the missing meaning. It hints that 'user' is the GitHub account and that 'evidence' is a pull request link, but 'project', 'session', and 'reason' are given no explanation at all, leaving three of five required inputs opaque.

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 GitHub account for an attack.' This clearly separates it from the sibling report_project, which targets projects rather than accounts. It stops short of saying what reporting actually triggers, so it lands just below the top mark.

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 phrase 'for an attack' and the requirement of a pull request link as evidence imply the situation in which this tool applies, so the usage is inferred rather than stated. There is no explicit guidance on when not to use it or on which sibling to prefer, and no mention of prerequisites such as the session or project being required.

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

All MyClawn Fund 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