Moatless

Request a codebase

request_codebase

Posts a public request for a codebase nobody has listed yet, so sellers know someone wants it. Only post one when the user asks, or when search_codebases finds nothing that fits and the user agrees. Check list_codebase_requests first, and if a request already fits, tell the user to upvote it on the website instead. Write it in the user's words: what they need, and anything that matters to them, like the stack. budget_cents is what they'd pay, only if they say.

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": {
      "input": "<input>"
    },
    "name": "request_codebase"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / input / properties / details / maxLength
```
Added value: +2000
```
- addedInput schema / properties / input / properties / title / maxLength
```
Added value: +120
```
- addedInput schema / properties / input / properties / title / minLength
```
Added value: +4
```
AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations give openWorldHint=true and destructiveHint=false, and the description adds genuinely new context: the request is public and visible to sellers, and duplicate requests should be redirected to upvoting rather than created. It does not mention auth requirements or what happens after posting, keeping it just short of 5.

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?

Five short sentences, front-loaded with the core action, then guidance, then parameter notes. Every sentence carries distinct information; only slight redundancy between the title phrasing in the description and the schema's 'What they need, in a line.'

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

Completeness4/5

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

No output schema exists, so an agent does not know what is returned (an ID? a URL?) — a real if small gap. Otherwise the definition covers the decision logic, the alternative tools, and the meaning of each nested field, which is enough to invoke it correctly.

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

Parameters4/5

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

Top-level schema coverage is reported as 0%, so the description carries the burden — and it does: title is 'what they need' in the user's words, details should include stack and requirements, and budget_cents is explicitly conditional ('only if they say'). Minor gap: no length or formatting guidance beyond what the nested schema already enforces.

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?

States a specific verb and resource — 'Posts a public request for a codebase nobody has listed yet' — and immediately clarifies the audience ('so sellers know someone wants it'). This is clearly distinguishable from search_codebases (find existing) and list_codebase_requests (browse existing requests).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit gating: only post when the user asks, or when search_codebases finds nothing AND the user agrees. It also names the prerequisite check (list_codebase_requests) and the preferred alternative action (tell the user to upvote on the website) when a match exists.

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

All Moatless tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?