Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

resolve_variables

Preview the configuration keys a project or service will receive before deployment, showing each key's winning scope and whether it is plain, without exposing secret values.

Instructions

What a launch would see: per key, the winning scope and whether it is plain. No values.

    The loop is "the agent asks, the human supplies". Call this before a
    deploy to see which keys the service will receive (``scope`` is
    ``project`` or ``production/<service>``). When a key the app needs is
    missing, do NOT invent or request the value in chat: ask the human to
    run ``nerdit vars set <project> --secret --prompt KEY``, then call this
    again to confirm the key is present. A secret value is never returned by
    any tool. Owner or admin only; a name outside your scope is 403.

Input Schema

NameRequiredDescriptionDefault
projectYesImmutable prj_ ID or name of an existing project. Prefer the ID from list_projects: a retired ID never addresses a same-name replacement.
serviceNoService inside the project whose launch to resolve for; omit for ``web``, the service of a single-app project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that no values are returned, secret values are never returned by any tool, access is owner/admin only, and out-of-scope names produce 403. It also explains the missing-key workflow, which is important agent behavior not captured by annotations.

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?

The description is front-loaded with the return shape and scope, then moves directly into the deploy-time usage and missing-key workflow. Despite covering several behaviors, every sentence contributes to correct invocation and safe handling of secrets.

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?

There is no output schema and no annotations, so the description must explain return semantics, safety, and permissions; it does all three. An agent knows what the tool returns, when to call it, how to handle missing keys, and that secret values will never be exposed.

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 coverage is 100%, so project and service are already documented in the schema, including the prj_ ID preference and web default. The description adds context about scopes and service launches but does not add parameter-level syntax or constraints beyond what the schema provides.

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?

The description states a specific operation and result shape: resolving what a launch would see per key, including winning scope and whether it is plain, with "No values." It clearly contrasts with mutation tools like set_variable by emphasizing inspection only and never returning secret values.

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

Usage Guidelines5/5

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

It explicitly says to call this before a deploy to see which keys the service will receive, and it gives a precise recovery path when a key is missing: ask the human to run `nerdit vars set <project> --secret --prompt KEY`, then call again. It also states what not to do: do not invent values or request them in chat.

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