Skip to main content
Glama

Open repository secret settings

repo_secret_settings
Read-onlyIdempotent

Return only the dashboard URL for securely setting, rotating or updating repository secrets. Does not accept or read secret values, or change settings. Any workspace member; writes in the dashboard require admin or owner.

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": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>"
    },
    "name": "repo_secret_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesThe repository id from get_workspace.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

It goes beyond the read-only and idempotent annotations by explaining that the tool only hands back a dashboard URL, never reads or accepts secret values, and does not change settings. It also discloses the authorization model: any workspace member may call it, but dashboard writes require admin or owner, which is exactly the kind of context an agent needs before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the return contract front-loaded, followed by the explicit non-goals and permission caveat. Nothing is wasted.

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 two-parameter, read-only tool with no output schema, the description covers the return value, the non-goals, and the permission requirements. An agent has everything it needs to decide whether and how to call it.

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%, so repo_id and workspace_id are already documented in the schema. The description adds no further meaning about those parameters, which is acceptable but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: it returns only the dashboard URL for setting, rotating, or updating repository secrets. That clearly separates it from sibling tools like list_repo_secrets and remove_repo_secret, though it never names an alternative explicitly.

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?

It states the intended use case (securely setting, rotating, or updating secrets) and explicitly rules out accepting or reading secret values, which tells the agent to look elsewhere for read operations. It stops short of naming the specific alternative tool, so the routing guidance is clear but implicit.

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