perseus

perseus_auto_skill

Read-only

Specify a skill for the agent to load before beginning work. Enforces critical hygiene skills like memory-hygiene or agent-safety at the top of context documents.

Instructions

Instruct the agent to load a specific skill before starting work. Use at the top of context documents to enforce critical hygiene skills (e.g., memory-hygiene, agent-safety). Renders as a mandatory instruction block. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "perseus_auto_skill"
  }
}

Input Schema

Name	Required	Description	Default
`skill`	No	Name of the skill the agent should load before beginning work

Output Schema

Name	Required	Description	Default
`rendered`	No	Resolved directive output as markdown

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.10Jun 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Discloses that the tool renders as a mandatory instruction block, adding context beyond the readOnlyHint annotation. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences front-loaded with purpose, then usage guidance, then behavioral note. No redundant text.

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?

Description adequately covers purpose and usage for this simple tool. Even with output schema present, no need to elaborate further.

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 provides full parameter description. Tool description adds minimal value with examples but doesn't specify syntax or format beyond schema. 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?

Clearly states the tool instructs the agent to load a specific skill. Uses specific verb 'load' and resource 'skill'. Distinguishes effectively from sibling 'perseus_skills' which likely lists skills.

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

Usage Guidelines4/5

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

Explicitly advises use at the top of context documents for enforcing critical hygiene skills, with concrete examples. Lacks explicit when-not-to-use guidance, but context is clear.

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