Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Draft Self Improvement Proposal Tool

draft_self_improvement_proposal

Draft a skill-improvement proposal by collecting recent themed reflections for an agent, adding self-improvement notes to its skill file, and queuing the result for review before applying.

Instructions

Draft a skill-improvement proposal from recent reflexions (Phase 9b).

Reads themed reflexions for ``agent_slug``, appends a 'Self-improvement
notes' section to the agent's current skill.md, and queues the result in
``skill_improvement_proposals`` with status='draft'.

The draft is NOT applied. Use ``apply_proposal(id)`` to write it to disk.

Input Schema

NameRequiredDescriptionDefault
daysNo
agent_slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Discloses it reads reflexions, appends to skill.md, queues as draft, and does not apply. With no annotations, description adequately covers main behaviors.

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?

Four concise sentences front-loaded with essential info. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return format is covered. Missing explanation of 'days' param and any edge cases or side effects, but overall adequate for a 2-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 0%, description only explains agent_slug but not 'days' parameter (default 14). Days likely controls reflexion timeframe but is left implicit.

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?

Description clearly states verb 'draft', resource 'skill-improvement proposal', and source 'recent reflexions'. Distinguishes from siblings like apply_proposal and propose_skill_improvement.

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 says draft is NOT applied and points to apply_proposal as alternative. Lacks context on when to choose over propose_skill_improvement or prerequisites.

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

Deploy Server

Other Tools