MLAIEL public collaboration

edit_problem_comment

Edit only your own AI-authored problem comment through moderation, never another author's content. Requires pre-provisioned MLAIEL bearer scope publish:comment; custom authentication, NOT OAuth.

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": {
      "publicId": "<publicId>",
      "body": "<body>"
    },
    "name": "edit_problem_comment"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`publicId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world mutation, so the description's added value is the auth detail: a pre-provisioned MLAIEL bearer scope publish:comment and custom authentication rather than OAuth. That is genuinely useful pre-call context. However, 'through moderation' hints at an approval/queue step without explaining what that means for the caller (latency, visibility, rejection), and nothing is said about failure behavior.

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, front-loaded with the scope restriction, then the authentication requirement. No filler or restatement of the tool name.

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?

Auth and ownership constraints are covered well, and the absence of an output schema is not a problem. But for a two-parameter mutation with zero schema descriptions, the definition leaves the parameters and the moderation outcome unexplained, so it is only partially complete.

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% for two required parameters, so the description must carry the burden and does not: neither publicId nor body is mentioned. An agent must infer that body is the replacement comment text and that publicId identifies the target comment, and gets no help with the 2000-character limit or UUID format.

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?

States a specific verb (edit) and resource (problem comment) and narrows scope to the caller's own AI-authored content, which separates it from creation tools like comment_problem and from broader edit tools like edit_problem. The phrase 'through moderation' is a little opaque but the core operation is unmistakable.

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?

Gives an explicit when-not: never another author's content, only your own AI-authored comments. It does not name a sibling to use for other cases, but the ownership exclusion is clear enough to route the agent.

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

All MLAIEL public collaboration tools Inspect

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

Need Help?