Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

load_skill

Read-onlyIdempotent

Load one of your skills: the full instructions for doing something, which the turn only announced by name. Do it BEFORE working in a skill's area rather than after -- the announcement says what a skill is for, and the skill itself says how, including which calls to make and what not to do. Pass a section name to load only part of it. A skill may also carry FILES it tells you to read -- a lookup table, a mapping -- and resources names them; pass one as resource to be given it. Asking for a skill, a section or a resource that does not exist returns the ones that do.

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": {
      "skill": "<skill>"
    },
    "name": "load_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesWhich skill, by the name the turn announced.
sectionNoOne section of it, by heading. Omit for the whole skill.
resourceNoOne file the skill carries, by name, as `resources` lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/no-destructive, so the safety profile is covered. The description adds real context beyond that: a skill may carry files, and invalid skill/section/resource requests return the valid options rather than failing. It does not describe the full return shape, but with no output schema a 4 is fair.

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?

The timing directive is front-loaded and every sentence carries information: when to use, what the payload contains, how to narrow with section/resource, and error behavior. The prose is dense with em-dashes and backticked param names, which slows reading slightly, but nothing is redundant.

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?

Covers purpose, timing, partial loading, bundled files, and the not-found fallback — everything needed to invoke correctly against a 3-param read-only tool. Without an output schema, a little more on what the returned instructions/resources look like would close the remaining gap.

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. The description earns a bump by explaining the relationship between parameters — that `resources` on a skill names files you then pass to `resource`, and that `section` narrows to one heading — which ties the three params into a coherent lookup flow rather than three isolated strings.

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?

"Load one of your skills: the full instructions for doing something" gives a clear verb and resource and defines 'skill' as the full instruction set that a turn only announced by name. It is distinguishable from siblings like kb_get_document, though the boundary with the knowledge-base tools is left implicit rather than stated.

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?

Explicitly states when to call it: "Do it BEFORE working in a skill's area rather than after," and explains why the announcement is not enough. This is a genuine sequencing rule an agent cannot infer from the name or schema.

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

All MangroveAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources