Skip to main content
Glama

guest_config

Read-onlyIdempotent

Read selected resource configuration for one scoped guest by guest ID, enabling quick inspection of a virtual machine or container's settings.

Instructions

Read selected resource configuration of one scoped guest.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guest_id": "<guest_id>"
    },
    "name": "guest_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
guest_idYesA guest identifier permitted by startup configuration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the scoping word "scoped", which hints at startup-configuration-based access limits but never states what gets returned, whether any fields are redacted, or whether reads can fail for out-of-scope guests.

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

Conciseness4/5

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

A single short sentence with no filler and the key qualifier (one scoped guest) up front. It is efficient, though the terseness comes at the cost of specifying what configuration is actually returned.

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?

With one parameter, rich annotations, and no output schema, the definition is close to adequate, but it never says which configuration domains are included or what the response looks like. For a read tool with an undefined payload, that leaves a meaningful gap an agent would want filled.

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% and the single guest_id parameter is documented with bounds and the "permitted by startup configuration" constraint. The description's phrase "one scoped guest" reinforces the single-ID semantics but adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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?

"Read selected resource configuration of one scoped guest" gives a verb (Read) and a target (guest resource config), so it is not a tautology. But "selected resource configuration" is never defined — an agent cannot tell whether this covers CPU/memory allocation, disks, network interfaces, or all of them. It is distinguishable from list_guests and guest_snapshots only by the word "configuration".

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 alternatives such as node_status or storage_status, and no exclusions. The agent must infer usage purely from the phrase "one scoped guest", which only implicitly says this is a single-guest lookup.

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