Skip to main content
Glama

Get a kit

get_kit
Read-onlyIdempotent

List the Durability Curve's paid kits (each tests one guard on the user's own machine: permission rules, prompt injection, test locks, hooks, skills), or get one. For a paid subscriber, a kit comes with its download address, its sha256 and the steps for you to run it, which start by asking the user. Free: what each kit tests, what it needs and the guide it belongs to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kitNoWhich kit. Leave it out to list the kits on the Kits tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds non-inferable behavior: the paid path returns a download URL plus sha256 and run steps, and those steps 'start by asking the user', which signals an imminent user prompt. The free path's reduced payload is also disclosed. It does not state auth requirements or what happens for a non-subscriber requesting a specific kit.

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?

Two sentences, front-loaded with the list/get split and zero filler. The second sentence is dense and the 'Free:' fragment is telegraphic, which slightly costs readability but not meaning.

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?

With no output schema, the description carries the return-value burden and does so for both the paid and free cases. Gaps are minor for a one-param read tool: no error behavior for an unknown kit and no mention of auth or rate limits.

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% and the enum already documents each value, so the baseline is 3; the description earns an extra point by mapping the five enum values onto the guard concepts they test (permission rules, prompt injection, test locks, hooks, skills). It adds little about the omit-behavior beyond what the schema description already says.

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?

States a concrete verb and resource ('List the Durability Curve's paid kits ... or get one') and explains what a kit is (each tests one guard on the user's own machine). The dual list/get behavior is clear, but the phrasing 'or get one' is abrupt and the domain term 'Durability Curve' is never grounded, so an agent outside that product context must infer.

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 implied through the outcome split: supplying a kit yields download address/sha256/steps, omitting it lists kits on the Kits tab. There is no explicit when-to-use/when-not guidance and no alternative tool is named, so routing to siblings like check_agent_setup is left to inference.

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