Engram

Load Skill Guide

engram_skill

Read-onlyIdempotent

Find a procedural checklist before a repeatable task. Omit skill or pass an empty string to list available names; otherwise load a name such as code-review or skill:code-review.

Returns JSON with available_skills/usage for listing or skill/count/steps/combined for a guide. Unknown names return count=0 and a message. Reads workspace/public knowledge without installing or executing anything. Use engram_recall for a project fact and engram_smarter for task-based guide selection. Consumes workspace daily call quota. OAuth: memory:read.

Input Schema

Name	Required	Description	Default
`skill`	No	Checklist name, e.g. code-review, security or skill:deployment. Omit or pass an empty string to list available names; unknown names return count=0.

Output Schema

Name	Required	Description
`text`	Yes	The same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool.
`format`	Yes	Payload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text.
`truncated`	Yes	True when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / skill / description

Added value: +"Checklist name, e.g. code-review, security or skill:deployment. Omit or pass an empty string to list available names; unknown names return count=0."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "format": {
+      "description": "Payload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text.",
+      "enum": [
+        "markdown",
+        "json",
+        "text"
+      ],
+      "type": "string"
+    },
+    "text": {
+      "description": "The same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "text",
+    "format",
+    "truncated"
+  ],
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, but the description adds non-obvious operational facts: it 'reads workspace/public knowledge without installing or executing anything', it 'consumes workspace daily call quota', and it requires OAuth scope 'memory:read'. Quota and auth disclosure are exactly the behavioral context annotations cannot convey.

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 purpose, then parameter behavior, return shapes, alternatives, then side effects and auth. Dense but every sentence is actionable. Minor redundancy in enumerating return fields that the output schema already covers.

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?

Given the single optional parameter, an output schema, and full annotations, the description covers everything an agent needs: purpose, both invocation modes, failure behavior, alternative tools, quota cost, and auth scope. No gaps for this tool's complexity.

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 single parameter's description already documents the omit/empty-string-to-list behavior and the count=0 unknown-name result. The description largely restates this, adding only the 'skill:' prefix example, which the schema already shows via 'skill:deployment'. Baseline 3 applies.

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 — 'Find a procedural checklist before a repeatable task' — and immediately distinguishes itself from siblings by naming engram_recall (project facts) and engram_smarter (task-based guide selection). An agent can tell what this does and where it fits without opening another 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 explicit routing rules: the no-argument/empty-string path for listing, named path for loading, and two named alternatives with the conditions that select them ('Use engram_recall for a project fact and engram_smarter for task-based guide selection'). Nothing 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.

All Engram tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?