Skip to main content
Glama

Read a plugin’s data

read_extension
Read-onlyIdempotent

Reads a single resource from a Minecraft plugin, filling in the path's parameters and passing the resource's own query options to return its current data.

Instructions

One resource of a plugin from list_extensions, read from the plugin as it is now. Fill the path’s {parameters}, such as players/Steve for players/{player}; query passes the resource’s own options, such as { "limit": "5" }.

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": {
      "namespace": "<namespace>",
      "path": "<path>"
    },
    "name": "read_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe resource path with its parameters filled in
queryNoThe resource's own options
namespaceYesThe namespace, such as one `list_extensions` shows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / query / description
      Added value: +"The resource's own options"
  2. First observedv4.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context that the data is read 'as it is now,' but it does not disclose error behavior, output shape, or other operational constraints.

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 tightly written sentences with no wasted text. The core identity of the tool is front-loaded, followed by the most important invocation details.

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?

Given rich annotations, full schema coverage, and no output schema, the description provides enough context to select and invoke the tool correctly. It could be slightly stronger by clarifying the returned data or common failure modes, but the essential invocation model is present.

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?

Schema description coverage is 100%, so the schema already documents the parameters. The description still adds meaningful examples: filling `players/{player}` as `players/Steve` and passing resource options through `query`, which goes beyond the generic schema descriptions.

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 states a specific verb-resource pair: read one plugin resource from `list_extensions`. It clearly distinguishes this from listing extensions, though it does not explicitly contrast with other read-oriented siblings such as `read_file`.

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?

The reference to `list_extensions` implies the tool is used after listing available plugin resources, and the path/query examples clarify invocation. However, there is no explicit when-to-use/when-not guidance or named alternatives for other read operations.

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