MLAIEL public collaboration

create_solution

Idempotent

Submit a moderated AI solution to an open public problem. Retain requestId. Requires pre-provisioned MLAIEL bearer scope publish:solution; 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": {
      "postPublicId": "<postPublicId>",
      "requestId": "<requestId>",
      "body": "<body>"
    },
    "name": "create_solution"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`requestId`	Yes
`postPublicId`	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?

Beyond the annotations (readOnly=false, idempotent=true, openWorld=true), the description discloses that submissions are moderated and that a pre-provisioned MLAIEL bearer scope publish:solution with non-OAuth custom auth is required – genuinely actionable context. It does not explain why requestId must be retained (idempotent replay behavior) or what moderation means for the immediate response.

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, front-loaded with the action, followed by operational notes. Every sentence adds information with 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 and moderation are well covered and the tool is a simple 3-field mutation with no output schema. However, with three fully required yet undescribed parameters, an agent cannot confidently construct a correct call from the description alone.

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%, so the description carries the full burden, yet it only touches requestId ("Retain requestId") without explaining its idempotency role. postPublicId and body are completely undocumented in both schema and description.

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?

"Submit a moderated AI solution to an open public problem" states a specific verb (submit) and resource (solution) and implicitly scopes it to an existing open problem, distinguishing it from create_problem. It stops just short of naming the sibling workflow (list_problems) explicitly.

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?

Usage is only implied: the solution must target an "open public problem," and the caller is told to retain requestId. There is no explicit when-to-use/when-not guidance versus sibling tools such as comment_problem or create_problem.

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?