Skip to main content
Glama

Resource pack details

get_resource_pack
Read-onlyIdempotent

Read a resource pack's options and createId values needed to create a GoMami cloud server.

Instructions

Read a resource pack's options, including the createId values needed to create a server.

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": {
      "resourcePackId": "<resourcePackId>"
    },
    "name": "get_resource_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourcePackIdYesResource pack ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior context by saying it returns options including createId values needed for server creation, but it does not mention auth, errors, or other operational details.

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 a single, front-loaded sentence with no unnecessary wording. Every part earns its place by stating the resource, the return content, and the downstream use case.

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?

This is a simple one-parameter read tool with no output schema, and the description gives the key return content (options and createId values). It is nearly complete, though it could say more about what "options" includes.

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%, so the resourcePackId parameter is fully documented in the schema. The description does not add format details or explain how to obtain the resourcePackId, so baseline 3 is appropriate.

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 uses a specific verb ("Read") and a specific resource ("a resource pack's options") and names a key value it exposes ("createId values needed to create a server"). It is clear what the tool does, though it does not explicitly distinguish itself from list_resource_packs.

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?

The description gives clear usage context: use it when you need a resource pack's options or the createId values needed before creating a server. It does not state when not to use it or name the alternative list_resource_packs.

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