Skip to main content
Glama
Sign In
SkullRender-Agents MCP Server

SkullRender-Agents MCP Server

by crozzbite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

skflow_pack_get

Retrieve a personality pack's full YAML by its ID, exposing the entire configuration for validation or integration.

Instructions

Get full YAML of one personality pack by id (e.g. PackLich).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the output is 'full YAML' and that it operates by id, implying a read-only operation. However, it does not mention error behavior, permissions, or any side effects, which are not critical for a simple getter but would add transparency.

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?

The description is a single sentence that is front-loaded with the verb 'Get', immediately states the resource and scope, and ends with a helpful example. No wasted words.

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?

For a tool with one parameter and no output schema, the description is complete: it states what is returned (full YAML), how to specify which pack (by id), and gives an example. It does not need to detail error cases or list alternatives given its simplicity.

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?

Schema coverage is 0%, so the description must compensate. It adds meaning by identifying the parameter as the pack id and providing a concrete example ('PackLich'). This is sufficient for a single simple parameter, though it does not specify id format beyond the example.

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?

The description clearly states the specific action: 'Get full YAML of one personality pack by id' with a concrete example 'PackLich'. It distinguishes this from sibling tools like skflow_packs_list, which lists packs, by focusing on retrieving a single pack's full YAML.

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?

The description provides clear context for when to use the tool: when you have a specific pack id and need its full YAML. It does not explicitly mention alternatives or exclusions, but the usage context is clear enough for a simple getter tool.

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