R3

Where a shared code module is used

r3_module_usage

Read-onlyIdempotent

Which of this account's projects (and entity templates) import one of your code modules: per project the scripts that import it, the version it runs, and whether that version is pinned or follows the latest. Projects of other accounts that import a public module of yours are only counted.

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>"
    },
    "name": "r3_module_usage"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Your module's name, e.g. "ship-core".

Output Schema

Name	Required	Description
`name`	Yes
`answer`	Yes	This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
`moduleId`	Yes
`projects`	Yes
`templates`	Yes
`latestVersion`	Yes
`otherAccounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent, read-only, open-world operation, so the description's job is to add substance — and it does, disclosing the exact return shape (per-project importing scripts, running version, pinned vs latest) and the cross-account rule that foreign projects are only counted rather than enumerated.

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?

A single dense sentence with the resource and the return payload front-loaded and no wasted preamble. The trailing clause about other accounts ('are only counted') is slightly awkward but earns its place by defining cross-account behavior.

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?

With an output schema present and full annotation coverage, the description only needs to establish scope and semantics, which it does for a one-parameter read tool. The phrase 'are only counted' is mildly ambiguous about exactly how foreign-account usage surfaces, leaving a small gap.

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

Parameters3/5

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

Schema coverage is 100% and the single `name` parameter is already documented with a format pattern and example, so the schema carries the burden. The description only adds that the name refers to one of your own modules, which is marginal beyond what the schema provides.

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 reverse-lookup action (find which projects import a given module) plus the exact payload: per-project scripts, version, and pin status. An agent can distinguish this from r3_module_list, r3_module_read, and r3_module_pin without opening any schema.

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?

Scope is defined (this account's projects and entity templates; other accounts' projects only counted), which implies when the tool applies, but there is no explicit when-to-use statement or routing to alternatives such as r3_module_read for the module's own contents.

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

All R3 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?