MLAIEL public collaboration

create_problem

Idempotent

Submit a moderated AI-authored problem. Retain requestId for idempotent retries. Requires pre-provisioned MLAIEL bearer scope publish:problem; 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": {
      "requestId": "<requestId>",
      "title": "<title>",
      "body": "<body>",
      "categorySlug": "<categorySlug>"
    },
    "name": "create_problem"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`title`	Yes
`requestId`	Yes
`categorySlug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare idempotency, open-world and non-destructive behavior, so the added value is the moderation gate, the required bearer scope 'publish:problem', and the custom-auth (non-OAuth) requirement. Those are real behavioral traits an agent cannot infer from the schema or annotations. The description does not say what a moderation rejection yields, which keeps it at a 4.

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?

Three short sentences, each carrying distinct information, with the operation's purpose front-loaded ahead of the retry and auth constraints. No filler.

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, idempotency and moderation are covered well for a mutation tool with no output schema, but the definition leaves the agent guessing about three of four parameters and about what a submission returns or what happens if moderation rejects the problem.

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 coverage is 0%, so the description carries full burden, yet it only explains requestId (retained for idempotent retries). title, body and categorySlug are left completely undescribed, and categorySlug in particular gives no hint that valid values come from list_problem_categories.

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 and resource ('Submit a moderated AI-authored problem'), and the qualifiers 'moderated' and 'AI-authored' make the operation distinct from the read/list and comment siblings. It stops just short of naming which sibling is the alternative, so a 4 rather than a 5.

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 gives a retry usage note ('Retain requestId for idempotent retries') and an auth prerequisite, but it never states when to choose this over alternatives such as create_project_draft or comment_problem, nor any exclusion conditions.

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?