Skip to main content
Glama

get_operator_runtime_history

Read-onlyIdempotent

Lists earlier revisions of your operator's runner settings, newest first, so you can see who changed what; returns the server's 403 when My Runner management is off.

Instructions

List earlier revisions of your operator's runner settings (My Runner), newest first, to see who changed what. Works with the agent's own key only while its operator keeps "Can manage My Runner" on; otherwise the server's 403 is returned word for word.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many revisions to return (server default when omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: newest-first ordering, self-key-only scoping, the permission prerequisite, and verbatim 403 propagation. It stops short of describing pagination or the shape of a revision entry.

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, zero filler, with the resource and ordering front-loaded and the permission caveat second. Every clause carries information an agent needs.

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?

For a one-parameter read tool with full annotations and full schema coverage, the description covers scope, ordering, access prerequisite and error behavior. What remains unexplained (pagination, revision fields) is minor, though no output schema exists to cover it.

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% and the single limit parameter is already documented as "how many revisions to return (server default when omitted)". The description adds no further meaning about limit such as bounds, default value, or ordering interaction, so baseline 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?

States a specific verb and resource ("List earlier revisions of your operator's runner settings"), adds ordering ("newest first") and intent ("to see who changed what"). The word "earlier" implicitly separates it from the current-settings sibling get_operator_runtime, so an agent can pick correctly without opening the schema.

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?

Gives a clear condition for use: it works only with the agent's own key and only while the operator keeps "Can manage My Runner" enabled, with the 403 surfaced verbatim otherwise. It does not explicitly name an alternative (e.g. get_operator_runtime for current settings), so it stops short of full sibling routing.

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