Skip to main content
Glama

Read repository environment status

get_repo_environment
Read-onlyIdempotent

Read repository environment status and setup updates. Any workspace member; requires the repository environments feature.

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": "get_repo_environment"
  }
}

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

B3.4/5.0
Behavior3/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 two genuinely new operational facts not present in the annotations: the caller permission level and the feature-flag dependency. It still doesn't explain what 'setup updates' means in the response, so the added value is partial.

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?

Two short sentences with the purpose front-loaded and the access constraints immediately after; no filler. Slight deduction because the trailing 'and setup updates' is vague wording that doesn't earn its place without elaboration.

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

Completeness3/5

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

For a simple two-parameter read tool with rich annotations and full schema coverage, this is close to complete: purpose, permission, and feature prerequisite are all stated. The remaining gap is that an agent cannot predict what 'environment status and setup updates' contains, and there is no output schema to compensate.

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%, including provenance hints ('from get_workspace', 'from whoami'), so the schema already carries full parameter meaning. The description adds no syntax, format, or constraint information beyond it, making the baseline 3 appropriate.

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?

Names a specific verb and resource ('Read repository environment status'), which cleanly separates it from config-writing siblings like set_repo_override. The appended 'and setup updates' is vague and doesn't tell the agent what that portion actually returns, so it falls short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description gives eligibility ('Any workspace member') and an environmental prerequisite ('requires the repository environments feature'), which is useful context for deciding whether calling is viable. It does not, however, say when to choose this over get_repo_config or preflight_repo_config, so usage routing remains 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