Skip to main content
Glama

Get loadout

get_loadout
Read-onlyIdempotent

Metadata for one loadout: description, agent compatibility, verification and agent-test status, requirements, and the file list with roles, sizes, raw URLs and per-agent install paths.

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": {
      "id": "<id>"
    },
    "name": "get_loadout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLoadout id, e.g. nextjs-supabase-saas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 closed-world scope, so the safety profile needs no restating. The description adds value by enumerating the returned fields and implicitly bounding scope (a file *list* with raw URLs and install paths, not file contents), but says nothing about behavior for an unknown id or any failure mode.

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 that identifies the resource first and then lists return fields. The enumeration is dense but each item earns its place given there is no output schema; no filler wording.

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?

For a one-parameter read tool with rich annotations, the description covers what comes back and implicitly distinguishes listed files from file contents. It is incomplete on routing between siblings and on what happens when the id does not exist.

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 coverage is 100% and the schema itself supplies the id slug pattern, length bounds and an example ('nextjs-supabase-saas'). The description adds no additional meaning about the identifier beyond that, so the baseline 3 applies.

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 single specific resource ('one loadout') and enumerates exactly what metadata is returned, so an agent can tell it apart from get_loadout_file (file contents) and search_loadouts (discovery). It lacks an explicit retrieval verb, but the resource scope is unambiguous.

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 statement of when to use this instead of search_loadouts or get_loadout_file, and no prerequisite or exclusion is given. Usage is only inferable from the singular 'one loadout' phrasing.

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.