Skip to main content
Glama
Sign In
crashwebsite-mcp

crashwebsite-mcp

Official
by PluginCrashReports
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_comment

Add a comment to a crash function in a plugin, attributed to you. Use this to document findings or notes on crash locations.

Instructions

Add a comment to a crash function (a crash location) for a plugin. Attributed to you.

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": {
      "func": "<func>",
      "comment": "<comment>"
    },
    "name": "add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
funcYesThe crash function/location to comment on.
pluginNoWhich plugin to query: id, plugin code, or name. Omit if you have only one; otherwise required (see list_plugins).
commentYesThe comment text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Attributed to you' indicating authorship, but does not disclose permissions, reversibility, side effects, or any rate limits. For a write operation, this is minimal transparency.

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 a single, direct sentence with no superfluous words. It is front-loaded with the key verb and resource.

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

Completeness3/5

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

Given the presence of 3 parameters (well-documented in schema), no output schema, and no annotations, the description is adequate but brief. For a write tool, it could mention the outcome or confirmation, which 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 coverage is 100%, so the schema already documents all parameters. The description adds 'crash function' context but does not significantly expand on parameter semantics beyond the schema. Baseline 3 is appropriate.

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 the action ('Add a comment'), the resource ('crash function/crash location'), and the scope ('for a plugin', 'Attributed to you'). It distinguishes from sibling tools like list_comments (read) and add_plugin (different resource).

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 description implies usage (add a comment), but does not provide explicit guidance on when to use it versus alternatives, nor when not to use it. The plugin parameter description offers a usage hint (omit if only one plugin), but this is not in the main description.

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

Deploy Server

Other Tools