MLAIEL public collaboration

edit_own_project

Edit only your own project story through moderation. No verification, financial or publication-policy controls. Requires pre-provisioned MLAIEL bearer scope publish:project; 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": {
      "name": "<name>",
      "tagline": "<tagline>",
      "summary": "<summary>",
      "problem": "<problem>",
      "audience": "<audience>",
      "whyItMatters": "<whyItMatters>",
      "publicId": "<publicId>"
    },
    "name": "edit_own_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`needs`	No
`problem`	Yes
`summary`	Yes
`tagline`	Yes
`audience`	Yes
`category`	No
`publicId`	Yes
`officialUrl`	No
`whyItMatters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

B3.2/5.0

Behavior4/5

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

The description adds substantial behavioral context beyond annotations: it discloses a moderation workflow, clarifies that no verification or financial/publication-policy controls apply, and specifies a custom authentication scope (MLA IEL bearer, NOT OAuth). This is valuable for a mutation tool with an open-world hint.

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 description is three tight sentences, front-loading the purpose and then layering behavioral and auth details. Every sentence adds value, though the phrase 'No verification, financial or publication-policy controls' could be slightly clearer.

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?

While the behavioral and auth context is strong, the complete absence of parameter semantics is a critical omission for a 10-parameter mutation tool. An agent would need to inspect the schema manually to know what to send, making the definition insufficiently complete.

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

Parameters1/5

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

The description provides zero information about the ten input parameters (seven required), and schema description coverage is 0%. For a tool with this many documented-only-by-name fields, the description completely fails to compensate for the schema gap.

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: 'Edit only your own project story through moderation.' This clearly identifies the action and scope (own project) and distinguishes it from siblings like delete_own_project or create_project, though it does not explicitly name alternatives.

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 'Edit only your own project story' implies when to use the tool, and the auth requirement sets a precondition. However, it offers no explicit when-not guidance or alternatives (e.g., use edit_problem for problem editing), leaving the agent to infer boundaries.

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?