Skip to main content
Glama
Sign In
Gud API MCP Server

Gud API MCP Server

Official
by gudlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

upsert_environment

Create or update a named set of variables, such as base_url and tokens, and optionally activate it for future API requests.

Instructions

Create or update an environment (a named set of variables, e.g. base_url and tokens). Matched by name. Optionally set it active for subsequent send_request calls.

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": {
      "name": "<name>",
      "variables": "<variables>"
    },
    "name": "upsert_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
setActiveNo
variablesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. Discloses upsert behavior and side effect of setting active environment, but does not explain update semantics (e.g., replace vs. merge variables), error conditions, or return value. Lacks detail on what 'set active' actually entails.

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?

Single sentence is concise, but could benefit from bullet points or structured explanation. Still, it is efficient with no wasted words.

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

Completeness2/5

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

Without output schema or annotations, the description should cover more. Missing information on return value, update behavior, error scenarios, and complete parameter details. Adequate only for the most trivial use case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet description only vaguely explains 'variables' with an example, missing details on the 'enabled' subfield and the required structure. 'setActive' is implied but not explicitly connected to the parameter name. Adds minimal value beyond the schema.

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?

Clearly states 'Create or update an environment' with examples, and implies upsert behavior via 'Matched by name'. However, lacks explicit differentiation from sibling tools like get_active_environment, which reduces clarity.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Mentions optional activation for send_request, but does not specify scenarios where other tools (e.g., upsert_request) would be more appropriate.

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

Deploy Server

Other Tools