Skip to main content
Glama

See what is in an R3 project

r3_project_load
Read-onlyIdempotent

List the components in an existing R3 project — what it contains and, for each one, its entityRef: the name code addresses it by (this['mesh_cube_1']). Read this before writing any code for a project, and after any tool call whose outcome was reported as unknown, to see what actually landed. Value components (Vector3, Color, Scalar) are not listed individually — reach them through their owner, e.g. mesh.position.x. Each object says which entity it belongs to (entity: {entityRef, id}, or null; r3_component_set {"entity": …} changes it), and an entityRef several components share (the same name in different entities) is listed with their ids: tools refuse that name, use the id.

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": {
      "projectId": "<projectId>"
    },
    "name": "r3_project_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project to read, from r3_project_create or the R3 app.

Output Schema

NameRequiredDescriptionDefault
nameYes
answerYesThis 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.
objectsYes
projectIdYes
componentCountYes
valueComponentCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / objects / items / properties / entity
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "entityRef": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "id": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "entityRef",
      +        "id"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / objects / items / required
      Previous value: -[
      -  "entityRef",
      -  "type",
      -  "name",
      -  "id"
      -]New value: +[
      +  "entityRef",
      +  "type",
      +  "name",
      +  "id",
      +  "entity"
      +]
  2. Changed2 schema fields changed
    • 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: -[
      -  "projectId",
      -  "name",
      -  "componentCount",
      -  "objects",
      -  "valueComponentCount"
      -]New value: +[
      +  "projectId",
      +  "name",
      +  "componentCount",
      +  "objects",
      +  "valueComponentCount",
      +  "answer"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavioral substance: value components are collapsed into their owners, each object reports entity ownership, and ambiguous shared entityRefs are listed with ids because tools refuse the bare name. It stops short of describing result size, depth of listing, or any limits on large projects.

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 the purpose, then layered with the entityRef details an agent actually needs before writing code. It is dense and the final sentence packs multiple ideas, but every clause carries non-obvious information rather than restating the schema or annotations.

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?

For a read-only listing tool with an output schema and full annotation coverage, this is nearly complete: it explains the entityRef concept, value-component omission, and the id-vs-name collision rule. The only gap is scope/size expectations for large projects, which an agent might want before calling.

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?

The single parameter projectId is fully documented in the schema (100% coverage, including provenance from r3_project_create), so the schema does the work. The description adds nothing about the parameter itself beyond the word "existing." Baseline 3 applies when coverage is complete.

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?

Opens with a specific verb and resource ("List the components in an existing R3 project") and immediately characterizes the return payload (entityRef plus the name code addresses it by). This clearly separates it from r3_project_list (which lists projects) and r3_component_read (which reads one component).

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

Usage Guidelines4/5

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

Gives explicit timing triggers: "Read this before writing any code for a project, and after any tool call whose outcome was reported as unknown." That is strong prescriptive context, but it never names a sibling as the alternative (e.g. r3_component_read for a single component, r3_project_changes for diffs), so routing is implied rather than enumerated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources