get_skillLoad an enabled SKILL.md and its supporting resource index.
Use after list_skills identifies a relevant skill. Load individual resources with get_skill_resource only when the skill instructions require them.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Slug of an enabled skill, usually obtained from list_skills. |
| Name | Required | Description | Default |
|---|---|---|---|
| skill | Yes | ||
| resources | Yes | ||
| instructions | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / slug / descriptionAdded value: +"Slug of an enabled skill, usually obtained from list_skills."Input schema / properties / slug / maxLengthAdded value: +100Input schema / properties / slug / minLengthAdded value: +1Input schema / properties / slug / patternAdded value: +"^[a-z0-9]+(?:-[a-z0-9]+)*$"Output schema / additionalPropertiesRemoved value: -trueOutput schema / propertiesAdded value: +{
+ "instructions": {
+ "type": "string"
+ },
+ "resources": {
+ "items": {
+ "properties": {
+ "content_type": {
+ "type": "string"
+ },
+ "path": {
+ "type": "string"
+ },
+ "size_bytes": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "path",
+ "content_type",
+ "size_bytes"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "skill": {
+ "properties": {
+ "created_at": {
+ "type": "string"
+ },
+ "description": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "file_count": {
+ "type": "integer"
+ },
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "source_agent": {
+ "type": "string"
+ },
+ "total_bytes": {
+ "type": "integer"
+ },
+ "version": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "description",
+ "version",
+ "source_agent",
+ "file_count",
+ "total_bytes",
+ "created_at"
+ ],
+ "type": "object"
+ }
+}Output schema / requiredAdded value: +[
+ "skill",
+ "instructions",
+ "resources"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations: it loads both the SKILL.md and its supporting resource index, only works on enabled skills, and clarifies that resources should not be loaded eagerly unless the skill instructions require them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundant wording. It front-loads the core action, then immediately provides the necessary sequencing and alternative-tool guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one well-documented parameter, strong safety annotations, an output schema, and a clear sibling distinction, the description is complete. An agent has everything needed to decide when and how to call this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides a complete description for the single parameter, slug, including format constraints and the hint that it usually comes from list_skills. The tool description adds no additional parameter-level meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and object: 'Load an enabled SKILL.md and its supporting resource index.' It also distinguishes itself from the sibling get_skill_resource by noting that individual resources should be loaded separately only when instructions require them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to use this tool after list_skills identifies a relevant skill, and directs when to prefer get_skill_resource instead. This is clear, actionable usage guidance with a named alternative and a selection condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly scoped purpose, and the descriptions include explicit usage rules that prevent overlap. Memory retrieval is split into read_context, search_memory, get_cluster, and export_all with distinct trigger conditions, so agents can reliably choose the right tool.
All tools use a consistent lower_snake_case verb_noun pattern such as list_clusters, get_skill, search_memory, write_observation, and upload_skill. The naming is predictable and uniform across the entire set.
Ten tools is well-scoped for a personal memory and skills server: it covers memory access, skill access, discovery, writing observations, and export. Each tool earns its place without the set feeling bloated or thin.
The server covers discovery, retrieval, saving observations, and uploading skills, but it lacks update/delete operations for memories and skill management beyond upload. This leaves a notable lifecycle gap: incorrect or obsolete saved observations cannot be removed or corrected in place.