Skip to main content
Glama

Get Free Skill

get_free_skill
Read-onlyIdempotent

Load a product's free gateway skill with its complete instructions. FREE.

Typical input {"slug": "inbox-commander"} returns {"slug": ..., "skill": "", "instructions": ""}.

Returns exactly one skill - the product's free gateway skill - chosen automatically from the slug, with no plan required. Use when the caller wants usable instructions immediately. Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""} (for example {"error": "unknown slug ''"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

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": {
      "slug": "<slug>"
    },
    "name": "get_free_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by search_catalog, e.g. "inbox-commander".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Product slug exactly as returned by search_catalog,\ne.g. \"inbox-zero-assistant\"."New value: +"Product slug exactly as returned by search_catalog,\ne.g. \"inbox-commander\"."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, but the description goes further: it discloses the error contract (never raises a protocol error, returns an {"error": ...} object with a fix hint), and states that retrying after correcting input is always safe. It also explains the automatic skill selection and that no plan is required.

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?

Front-loaded with the core action, then constraints, then error behavior. The inline example payloads consume space for modest benefit, but the rest is dense and every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool this is thorough: purpose, alternative routing, gating (free vs paid), error shape, and retry safety are all covered, and an output schema exists so return values need no further explanation.

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 already documents slug as 'exactly as returned by search_catalog' with an example. The description's example input/output shows how the slug drives selection, which is mild added value, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Load a product's free gateway skill with its complete instructions') and pins down the scope: exactly one skill, chosen automatically from the slug. It explicitly contrasts with get_full_skill, so the agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use when the caller wants usable instructions immediately') plus an explicit exclusion ('Not for the product's other skills... need get_full_skill with a skill_name, which requires a paid plan'). The alternative and the condition selecting it are named outright.

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.