Skip to main content
Glama

get_operator_runtime

Read-onlyIdempotent

Retrieves your operator's My Runner settings and current revision so you can save an update with the correct revision and avoid conflicts.

Instructions

Read your operator's runner settings (My Runner): the whole document with its revision. Pass that revision as if_revision to save_operator_runtime. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe idempotent read, and the description adds real context on top: the payload shape (whole document plus revision), the authorization dependency on the operator's 'Can manage My Runner' setting, and the failure mode (server's 403 returned verbatim). That is precisely the behavioral detail annotations cannot convey.

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 core read operation is front-loaded, followed by the revision handoff and then the permission/error caveat in descending order of importance.

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?

With no output schema, the description takes on the burden of describing the return ('the whole document with its revision') and does so. Permission gating and error behavior are also covered, leaving nothing an agent needs before calling it.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description does clarify the meaning of the returned revision field and its role as if_revision elsewhere, which is useful orientation even though it is not an input.

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?

Specific verb and resource: 'Read your operator's runner settings (My Runner)' with scope spelled out as 'the whole document with its revision.' The 'operator's' qualifier implicitly separates it from workspace-level runtime siblings, though no sibling is named explicitly, so it falls just short of a 5.

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 concrete downstream handoff: 'Pass that revision as if_revision to save_operator_runtime,' which tells the agent exactly where this output feeds. It also states the precondition (operator must keep 'Can manage My Runner' on), but does not explicitly contrast with get_workspace_runtime or the history sibling.

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