Skip to main content
Glama
Sign In
Gostman

Gostman

by kunalgoesbyken
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Recent changes

changes
Read-onlyIdempotent

Lists recently saved, imported, or modified requests and environments with their session, oldest first, so agents can review prior edits before touching the same items.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
mineNoOnly the changes this session made.
sinceNoHow far back to look, as a duration such as 5m or 2h. Defaults to 1h.

Output Schema

NameRequiredDescriptionDefault
changesNo
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing ordering (oldest first), workspace scoping, and that each entry carries the session that made the change, though it says nothing about result caps or pagination.

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?

Two sentences, no filler: the first front-loads what the tool returns and how it is ordered, the second gives the use case. Every clause earns its place.

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?

With rich annotations, full schema coverage and an output schema, the description only needs to supply purpose, scope and usage, all of which are present. The one small gap is that it does not indicate any limit on how many changes are returned for a given window.

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%, so 'mine' and 'since' (including the 1h default) are already fully documented. The description only implies the recency window through the word 'recently' and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb ('List') plus a precise resource ('requests and environments ... saved, imported or changed in this workspace recently') and states the ordering ('oldest first'). The change-feed framing, including the session attribution, clearly separates it from plain list tools such as list_requests or list_environments.

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 states an explicit use case: 'Use it to see what other agents changed before you edit the same items,' which tells the agent when this tool is the right pick. It does not name a when-not condition or a specific alternative, so it falls short of full routing guidance.

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