Skip to main content
Glama

Get a pack

get_pack
Read-onlyIdempotent

Status of a pack order and, when delivered, the manifest and download URL. Free.

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": {
      "order_id": "<order_id>"
    },
    "name": "get_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the response varies with delivery state, and only delivered orders yield a manifest and download URL, plus a 'Free' cost note. It still omits the set of possible status values and what happens for an unknown or failed order_id.

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 front-loaded sentence with zero filler; the conditional return info is properly subordinated. The trailing 'Free.' is terse and slightly fragmentary but does convey a real cost attribute rather than padding.

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 no output schema, the description must describe return values, and it partially does (status, conditional manifest and download URL). For a low-complexity, single-parameter read tool this is close to adequate, but the missing status enumeration and error behavior leave an agent guessing what a non-delivered response looks like.

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?

Only one parameter (order_id) and schema description coverage is 0%, so the description carries some burden. It ties order_id to a 'pack order', which gives the identifier's origin meaning, but it says nothing about format, where the id comes from, or whether expired ids are valid. Marginal value over the schema.

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 names a specific verb-and-resource pair (retrieve the status of a pack order) and even sketches the payload shape (manifest and download URL when delivered). It is clearly a read operation, implicitly contrasting with the sibling create_pack, but it never names that sibling or any other alternative explicitly.

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?

Usage is only implied: you call it with an order_id to check an existing pack order, which contrasts by implication with create_pack/create_preview. There is no explicit when-to-use/when-not statement, no prerequisite (e.g., that an order must already exist), and no mention of polling cadence for an in-progress order.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources