Skip to main content
Glama

Get loadout file

get_loadout_file
Read-onlyIdempotent

Raw contents of one file in a loadout (path as listed by get_loadout, e.g. AGENTS.md or skills/db-migration/SKILL.md). Max 100 KB.

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>",
      "path": "<path>"
    },
    "name": "get_loadout_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLoadout id, e.g. nextjs-supabase-saas
pathYesFile path within the loadout

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: the content is returned raw/unprocessed and there is a 100 KB ceiling. It does not say whether an oversized file is truncated or rejected, which leaves the limit's consequence slightly ambiguous.

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 short sentences with zero filler; the core purpose comes first and the example paths and size limit follow as qualifications. Nothing in it is redundant with the title.

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?

For a two-parameter read tool with full schema coverage and a complete annotation set, this covers nearly everything an agent needs: what is returned, how to obtain a valid path, and the size bound. The only gap is the unspecified behavior when a file exceeds 100 KB.

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 coverage is 100%, so the baseline is 3, but the description goes further by illustrating the expected path shape and framing it as relative to the loadout rather than an absolute filesystem path. That resolves the main ambiguity an agent would have about the `path` parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('raw contents of one file in a loadout') and scopes it to a single file, which cleanly separates it from the sibling get_loadout that lists files. The concrete path examples (AGENTS.md, skills/db-migration/SKILL.md) make the unit of work unambiguous.

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?

It supplies clear context: the path must be one 'as listed by get_loadout', which effectively tells the agent to enumerate first. There is no explicit when-not guidance or statement about what happens if a path is not in that listing, so it stops short of a full routing rule.

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.