R3

File a bug report about R3

r3_bug_report

Send R3 a bug report about R3 ITSELF (the engine, the editor, these tools), in the user's name and naming you (your agent key or app connection). It becomes one of the user's support issues, which only the user and R3's team see. Use it when R3 does something its documentation says it should not, after checking the docs (r3_docs_read) — not for problems in the user's own project, and not for feature wishes (those are r3_roadmap_suggest).

r3_bug_reports_mine lists what the user already reported, so a fault is not filed twice. A useful report says what was done (the tool calls), what was expected and what happened, with what was MEASURED in measurements — the values read back with r3_component_read or r3_editor_inspect, the exact error text. projectId (when it happens in a project) lets R3 open it. The answer carries the report's link for the user. Rate-limited per agent key or app connection (a few an hour). Needs the support:write right.

Input Schema

Name	Required	Description
`title`	Yes	One line naming the fault, e.g. "Cuboid collider with halfExtents.z = 0 inverts the contact normal".
`projectId`	No	The project it happens in (r3_project_list), if any. Only a project the user can open.
`description`	Yes	What you did, what you expected, what happened instead.
`measurements`	No	What you measured: values read back, exact error text, timings. Plain text.

Output Schema

Name	Required	Description
`url`	Yes
`title`	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.
`status`	Yes
`issueId`	Yes
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / answer

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "issueId",
-  "title",
-  "status",
-  "projectId",
-  "url"
-]New value: +[
+  "issueId",
+  "title",
+  "status",
+  "projectId",
+  "url",
+  "answer"
+]

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare write/open-world/non-idempotent; the description adds the substantive behavior: the report becomes a private support issue visible only to the user and R3's team, it is rate-limited per agent key or app connection (a few an hour), it requires the support:write right, the response carries a shareable link, and r3_bug_reports_mine exists to avoid duplicates. That is exactly the context annotations cannot convey.

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?

Front-loaded with purpose and identity in the first sentence, then routing/exclusions, then operational detail. The paragraph is dense and long, but each sentence carries a distinct constraint (docs check, dedup, measurements, visibility, rate limit, auth) rather than padding.

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

Completeness5/5

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

For a 4-param submission tool with an output schema already covering the return shape, the description supplies everything else an agent needs: prerequisites, exclusions, auth right, rate limit, visibility, dedup path, and expected report content. No material gap remains.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `measurements` should carry values read back with r3_component_read or r3_editor_inspect plus exact error text, and `projectId` is what lets R3 open the case. It also prescribes report content (what was done, expected, happened) beyond the terse schema phrasing.

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: send a bug report about R3 ITSELF (engine, editor, these tools), filed in the user's name. It explicitly scopes the subject away from the user's own project and from feature requests, so an agent can separate it from r3_roadmap_suggest or a project-level issue 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 Guidelines5/5

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

Gives the trigger condition ('when R3 does something its documentation says it should not'), a prerequisite ('after checking the docs (r3_docs_read)'), two explicit exclusions ('not for problems in the user's own project, and not for feature wishes'), and names the sibling to use instead for wishes (r3_roadmap_suggest). Nothing is left to inference.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?