Skip to main content
Glama

Read Stronghold actions

stronghold_protocol

Read and filter game action fields by type or prefix to avoid loading the entire catalog when inspecting or sending protocol commands.

Instructions

Read game action fields. Filter by type (e.g. g.move) or prefix (e.g. room.) to avoid loading the entire catalog.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that this is a read operation and hints at a performance concern by warning against loading the entire catalog, but it omits return format, pagination, error behavior, and how the two filters interact.

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?

The description is two tightly written sentences with no filler. The core action comes first, followed by the filtering guidance that directly affects invocation.

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?

The tool has two optional parameters, no annotations, and no output schema. The description covers the basic action and filtering intent, but it leaves the agent without a clear picture of the returned data or edge-case behavior, making it only minimally complete.

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 0%, so the description must add meaning. It gives examples for both parameters (type e.g. g.move, prefix e.g. room.) and explains their purpose, but it does not clarify prefix-matching semantics, whether filters combine with AND/OR, or what happens if both are supplied.

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?

The description gives a specific verb and resource: “Read game action fields,” and adds the available filtering modes. It does not explicitly differentiate this catalog-reading tool from siblings such as stronghold_lookup or stronghold_observe, so it falls 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 Guidelines3/5

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

It advises filtering by type or prefix to avoid loading the entire catalog, which gives practical usage context. However, it does not state when to choose this tool over alternatives such as stronghold_lookup or stronghold_observe, so usage remains implied rather than explicit.

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