Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Gostman sends HTTP, GraphQL and gRPC requests from the API collection kept in this workspace, the same one the developer uses in the Gostman app. Use these tools instead of curl in a shell: credentials are filled in from variables inside Gostman and never appear in a result, cookies, OAuth tokens and variables set by one request carry over to the next for as long as this server runs, and responses come back trimmed with their test results. Write {{name}} wherever a variable's value belongs. Text shown as {{name}} or {{redacted:...}} in a result is a value Gostman hid on purpose; you can keep using {{name}} in later requests, but you cannot read the value. A {{name}} that no variable defines is sent as it is; list_environments shows the defined names, and set_environment chooses the environment. Requests reach only localhost, the hosts the person's own requests use and hosts the developer allowed with --allow-host; when a host is refused, ask the developer to allow it instead of reaching it another way. A secret is filled in only for an address (scheme, host and port) that one of the developer's own requests sends it to; elsewhere its placeholder is sent as written and listed under withheld. To log in, give the login request an extractor with save_request so its token is kept as {{token}} without appearing in a result. Start with list_requests; import_requests adds requests from a spec or curl command.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_requestsA

List the API requests saved in this Gostman workspace: id, name, method, URL template, folder, tags, whether each has checks (hasTests) and whether it has saved example responses. Call this first to find a request to send instead of writing a curl command.

get_requestA

Show one saved request in full: URL, headers, body, auth settings, its own variables (vars), assertions, extraction rules, scripts and the names of its saved examples. Credentials are masked; variables appear as {{name}}. options lists only the settings that differ from the defaults. revision identifies this version for save_request.

send_requestA

Send a saved request (give request) or an ad hoc one (give url). Prefer this over curl in a shell: Gostman fills in {{variables}}, auth, cookies and OAuth tokens itself, so no secret has to appear in the command or in the result, and a login made by one call is still in effect for the next. Saved requests also run their scripts, extraction rules and assertions. Returns two parts: a JSON summary (status, duration, size, content type, the address as sent in resolvedUrl with variable values shown as {{name}}, test results, script console output, names of cookies and variables that were set, and body.bytes, body.returnedBytes, body.truncated) followed by the response body as text. When body.truncated is true, narrow the answer with select or raise max_body_bytes. failed is true when the request could not be sent or a test did not pass. unresolved lists placeholders that have no value; withheld lists secrets that were not filled in because none of the developer's requests sends them to this address.

run_folderA

Send every request in a folder, or in the whole workspace, in order, with scripts and assertions, the way the collection runner does. tags and exclude_tags narrow the run to a subset such as smoke tests; data and iterations repeat it. Use it to check that an API still works after a change. Returns the counts and, for failed requests only, the error, the failed checks (failedTests) and the console output.

last_responseA

Show the last response a saved request got in this session, from send_request or run_folder, without sending it again. When the request has saved examples, also compare the response with one: status, content type and, for JSON, the paths that differ.

save_requestA

Create a request in the workspace, or update one by id, so the developer finds it in the Gostman app and it can be re-run later. Only the fields you give are changed. Secrets are refused: a value that matches a variable or a credential must be written as {{name}}. Returns the request's id, name, folder and new revision. An update is refused when the request changed since you read it with get_request; read it again and merge.

import_requestsA

Add requests to the workspace from an OpenAPI or Swagger spec, a Postman, Insomnia or Bruno collection, a HAR file, .http requests or a curl command. Nothing existing is changed: the collection settings of a Gostman export are adopted only when the workspace has none. Scripts and OAuth 2.0 settings are removed (listed in leftOut; warnings describe the source document), and an import that holds a credential, reads local files or runs local commands is refused. Returns what was added.

list_environmentsA

List the environments of the workspace with the names of their variables, which one is active, and the names of the variables that have a value in this session. Values are never returned; reference a variable as {{name}}. Names under secret get their values from the developer; when one is missing from sessionVariables, ask the developer to pass it with --var-from-env.

set_environmentA

Choose the environment whose variables fill in {{name}} for the rest of this session, for example to switch from Local to Staging. The environment's variables are read again and variables set by earlier requests are cleared; cookies and OAuth tokens are kept.

set_variablesA

Save plain variable values such as baseUrl or userId in an environment file of the workspace, so later requests and the developer's app use them. Credentials are refused, and so are variables the developer marked secret. Values set here never let requests reach a new host. Refused when the environment changed since list_environments showed it.

changesA

List the requests and environments agents saved, imported or changed in this workspace recently, oldest first, with the session that did it. Use it to see what other agents changed before you edit the same items.

lint_specA

Check an OpenAPI 3 or Swagger 2 document against Gostman's built-in rules: missing operation ids or descriptions, undeclared path parameters, missing error responses, undefined security schemes, broken $refs and similar. Returns the counts and findings.

scan_secretsA

Look for credentials typed into the workspace's requests, environments, scripts and saved examples. Findings show where and why, with at most the first four characters of a value. Run it before the developer commits or shares the workspace.

load_testA

Send one saved request many times at once and report throughput, latency percentiles, status codes and error samples. Limited to 20 at once, 30 seconds and 5000 requests, to hosts this session may call. Only test systems the developer owns.

start_mockA

Start a mock server on localhost that answers each saved request's path with its saved example response. Use it to develop against an API that is not running. Returns the address and, per request, whether it is served and why not.

stop_mockA

Stop the mock server started with start_mock.

mock_statusA

Report whether the mock server is running, its address, its routes refreshed from the workspace, and the last requests it answered.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 17 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action: the mock trio (start/stop/status), request CRUD (list/get/save), and execution tools (send_request, run_folder, load_test) each have explicit boundaries spelled out in the descriptions. The only real friction is the environment trio (list_environments / set_environment / set_variables) and the send/run/load family, which an agent must read carefully to choose between, but the descriptions do resolve them.

Naming Consistency4/5

Roughly 13 of 17 names follow a clean verb_noun pattern (get_request, save_request, list_requests, start_mock, send_request, run_folder, lint_spec, etc.). The deviations are noun-only names like changes, last_response and mock_status, which are readable but break the otherwise predictable convention.

Tool Count4/5

17 tools maps well onto the breadth of the domain — workspace requests, environments, mocking, test runs, imports and linting — and each tool plausibly earns its place. It sits at the upper end of a comfortable set and a couple of the mock/status tools could conceivably be folded together, but nothing is redundant filler.

Completeness3/5

The core lifecycle is covered — list/get/save requests, send, run a folder, load test, import, mock serving, environment selection, secrets scanning and spec linting. However there is no way to delete or archive a request, no create/delete environment, and no folder management, so agents will hit dead ends on cleanup and naming/structural operations.

Maintenance

ActivityActive
ResponsivenessUsually handled