Skip to main content
Glama

muninn_skill_registry

Read-onlyIdempotent

List the skills this user wrote and saved in Muninn, as a <muninn_skills> XML block (name, description and location of each). Only this account's own skills, never another user's. Consult a skill when the user's request matches it: open its instructions with muninn_memory_get, passing the id at the end of its location. Use it to see the user's current skills mid-session, for example right after they create one.

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": "muninn_skill_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety and mutability need no restating. The description adds genuinely useful behavior beyond that: the XML block return shape, and the per-account visibility restriction that no other user's skills appear. It says nothing about ordering, listing limits, or what happens when the user has no skills, which are the remaining behavioral gaps.

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?

Three tight sentences, front-loaded with what is returned and in what format, then scope, then the follow-up path. The final sentence ('Use it to see the user's current skills mid-session...') mildly restates the opening listing purpose, but each sentence otherwise earns its place.

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?

With no parameters, no output schema and no nesting, the description carries the full burden and meets it: it describes the return payload structure, ownership scope, when to invoke it, and how to act on the results. An agent has everything needed to call it and use the output correctly.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline for a zero-parameter tool is 4. The description does explain how the returned 'location' value feeds into muninn_memory_get, which is useful semantics about output rather than input.

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 (list the skills this user wrote and saved), the output shape (<muninn_skills> XML with name, description, location), and an explicit scope boundary ('only this account's own skills, never another user's'). This is enough for an agent to distinguish it from a skill-creation or skill-check sibling without opening any schema.

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?

Gives concrete triggers: consult a skill when the request matches it, and use this to see current skills mid-session, e.g. right after creation. It also routes the agent forward to muninn_memory_get with the id from the location field. It does not explicitly say when not to use it or name a contrasting listing alternative, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources