Skip to main content
Glama

Read a project's publish settings

r3_publish_settings_read
Read-onlyIdempotent

Read the publish settings of one of the user's own R3 projects in this environment — what the app's Deploy → Settings shows: Works on (keyboard / touch / both / not tested), the SEO title and description that search engines and link previews show, how the live page starts (Start button, first click, on load), its controls and badge. Also answers a SUGGESTION for Works on, from a scan of the project's code for keyboard / touch / pointer handlers — only a suggestion. r3_publish_settings_set changes them. Needs the project:read right.

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_publish_settings_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project id (r3_project_list).

Output Schema

NameRequiredDescriptionDefault
liveYes
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.
addressYes
galleryNo
worksOnYes
seoTitleYes
projectIdYes
environmentYes
portalSettingsYes
seoDescriptionYes
worksOnSuggestionYes
hiddenBecauseNoSourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / hiddenBecauseNoSources
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "physics",
      +      "code",
      +      "audio",
      +      "music"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / address
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "environment",
      -  "worksOn",
      -  "seoTitle",
      -  "seoDescription",
      -  "portalSettings",
      -  "worksOnSuggestion",
      -  "live",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "environment",
      +  "worksOn",
      +  "seoTitle",
      +  "seoDescription",
      +  "portalSettings",
      +  "worksOnSuggestion",
      +  "live",
      +  "address",
      +  "answer"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / gallery
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "examplePrompt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "featured": {
      +      "type": "boolean"
      +    },
      +    "hidden": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "featured",
      +    "hidden",
      +    "examplePrompt"
      +  ],
      +  "type": "object"
      +}
  4. 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",
      -  "environment",
      -  "worksOn",
      -  "seoTitle",
      -  "seoDescription",
      -  "portalSettings",
      -  "worksOnSuggestion",
      -  "live"
      -]New value: +[
      +  "projectId",
      +  "environment",
      +  "worksOn",
      +  "seoTitle",
      +  "seoDescription",
      +  "portalSettings",
      +  "worksOnSuggestion",
      +  "live",
      +  "answer"
      +]
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context beyond them: the access requirement ("Needs the project:read right"), the ownership/environment restriction, and the important caveat that the Works on SUGGESTION is derived from a code scan of keyboard/touch/pointer handlers and is "only a suggestion." That distinction between stored setting and inferred suggestion is exactly the kind of nuance 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?

The verb and resource are front-loaded, followed by a dense enumeration of returned fields, then the suggestion caveat, the sibling pointer, and the permission note. Every sentence carries information, though the field list and parenthetical alternatives make it longer than strictly necessary for a one-parameter read tool.

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 single-parameter read tool with an output schema present, the description covers what the agent needs: which project, what concept the call returns, the advisory nature of the Works on suggestion, the mutating alternative, and the required permission. Nothing needed to call it correctly is missing, and return-value detail is rightly left to the output schema.

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 description coverage is 100% and the single projectId parameter is already documented with a pointer to r3_project_list, so the schema does the heavy lifting. The description adds only the constraint that the project must be the user's own and in this environment, which is mild added meaning rather than syntax or format detail. Baseline 3 is appropriate.

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 ("Read the publish settings") and enumerates the concrete contents: Works on, SEO title/description, live-page start behavior, controls and badge. It scopes the object precisely to "one of the user's own R3 projects in this environment" and explicitly separates itself from r3_publish_settings_set, so an agent can distinguish it from siblings without opening schemas.

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 a clear read-vs-write routing rule by naming r3_publish_settings_set as the tool that "changes them," which is the primary ambiguity for this pair. It also flags that the Works on suggestion is advisory only, so an agent knows not to treat it as ground truth. It does not discuss when to prefer this over project-level tools like r3_publish_live, but the core selection decision is covered.

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