Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

skill_load

Load a skill playbook by ID and return its full JSON guidance—principles, phrases, tactic order, boundaries, and exit signals—so agents can ground call handling in the right strategy.

Instructions

Load the FULL skill playbook by id. Returns the complete JSON document: principles, scripted phrases, tactic priority list, boundaries, success/failure signals, exit strategy. Use the response to ground your next turns on the call — the playbook should drive your phrasing, tactic order, and exit decisions.

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": "skill_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSkill id (lowercase-hyphenated, e.g. "negotiate-bill-reduction").
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the shape of the returned document section by section, which is the main behavioral fact an agent needs. It does not state read-only semantics explicitly, nor what happens when an id is not found, but "Load" reads unambiguously as a retrieval with no mutation risk.

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 action and return payload, with no filler. The second sentence slightly overlaps with the first by re-listing what the playbook drives, but it earns its place as the only usage guidance present.

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?

No output schema exists, and the description compensates by enumerating the returned document's sections, which is the key gap a caller would otherwise have. For a two-parameter read tool this is nearly sufficient; a note on not-found behavior or document size is the only meaningful omission.

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 description coverage is 100%, with both `id` format and the `_account` override fully documented in the schema, so the baseline is 3. The description reinforces that lookup is by id and that the whole document is returned, but adds no meaning to `_account` or to id formatting beyond 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?

States a specific verb and resource ("Load the FULL skill playbook by id") and enumerates exactly what comes back (principles, scripted phrases, tactic priority list, boundaries, signals, exit strategy). The word "FULL" implicitly contrasts with a lighter listing tool, but no sibling is named, so differentiation from skill_list/skill_search is left to inference.

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?

The second sentence tells the agent how to use the result ("ground your next turns," drive phrasing, tactic order, exit decisions), which implies loading before a call. However, there is no explicit when-to-use versus skill_list or skill_search, and no stated condition or prerequisite for loading versus searching.

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