Skip to main content
Glama

status

Returns backend, permission, active keymap profile, and held-key details so agents can verify input control readiness before or during gameplay.

Instructions

Backend, permission state, active keymap profile, held keys.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned contents (backend, permission state, keymap profile, held keys), which is genuinely useful since there is no output schema, but it says nothing about whether the call is read-only, whether 'permission state' implies an OS permission prompt, or what a degraded/denied state looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no filler, but it reads as a bare field list rather than a structured sentence, and the leading 'Backend' term is unexplained. Terseness here shades into under-specification rather than efficient concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-param status tool the description is roughly proportionate, and with no output schema it does list the four reported values. It still omits what each value means and how to interpret a non-granted permission state, which is the main thing an agent would need.

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 there is no parameter semantics to compensate for; the description's field list is a bonus rather than a requirement. Baseline 4 applies for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what the tool reports (backend, permission state, active keymap profile, held keys), which is more informative than the bare name 'status'. However, it is a noun fragment with no verb or explicit statement that calling it returns a snapshot of current state, so the agent must infer that this is a read of runtime state rather than an action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of related siblings such as profiles or release_all, and no indication of when a status check is warranted (e.g., before key_down to confirm held keys). Usage must be entirely inferred from the name.

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