Skip to main content
Glama

Open Keys & settings

manageEnvironment
Read-onlyIdempotent

Return the link to an app’s Keys & settings page in Tofu’s dashboard. Environment values are entered by the human on that page; agent tools accept and return environment names and scopes only, with no secret plaintext. Optional projectId selects the app’s page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manageEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral guarantee beyond that: no secret plaintext is ever accepted or returned, and the human performs the value entry. It does not say whether the returned link is authenticated, expiring, or otherwise constrained.

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?

Three short sentences, front-loaded with what the tool returns, then the security invariant, then the parameter. Nothing is repeated from the schema or annotations and no sentence is filler.

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 one-optional-parameter, read-only link tool with no output schema, the description covers purpose, the hand-off model, the no-plaintext guarantee, and the parameter. The only remaining gap is what happens with no projectId and any lifetime/authentication property of the returned link.

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 description coverage is 0%, so the description must carry the single parameter, and it does: `projectId` is optional and 'selects the app's page', i.e. it scopes which app's Keys & settings link comes back. That meaning is not derivable from the bare uuid-format property. It does not specify the default behavior when projectId is omitted.

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 uses a specific verb and resource: 'Return the link to an app's Keys & settings page in Tofu's dashboard.' It also clarifies the tool's real role, which the name manageEnvironment obscures — it does not manage secrets, it points the human at a dashboard page. It stops short of naming a sibling it complements, so 4 rather than 5.

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 gives a clear condition for use: environment values must be entered by the human on that page, so an agent calls this to hand off. It also states the boundary of what agent tools can do ('accept and return environment names and scopes only'), which implicitly rules out expecting secret values back. No explicit alternative tool is named, so not a 5.

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