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

SkullRender-Agents MCP Server

by crozzbite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

skflow_agent_get

Retrieve the full YAML of an agent manifest by its ID. Use with agent list to identify available IDs.

Instructions

Get full YAML text of one agent manifest by id. Use skflow_agents_list for available ids.

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_agent_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesManifest id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool returns 'full YAML text,' which adds return-format context, but it doesn't disclose error behavior, authentication needs, or side effects. Since it's a simple read operation, this is adequate but not rich.

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 exactly two sentences, front-loaded with the core action, and contains no fluff. Every word earns its place, and the cross-reference to the list tool is efficient.

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 simple one-parameter get tool with no output schema, the description covers the purpose, the return type (YAML text), and how to obtain valid ids. It is reasonably complete, though it could optionally mention error behavior for invalid ids, but that is not critical for basic usage.

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?

The input schema already fully describes the single 'id' parameter as 'Manifest id field' (100% coverage). The description merely says 'by id,' which adds no new semantics beyond what the schema provides, so the baseline score of 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?

The description states a specific verb ('Get'), a specific resource ('agent manifest'), and the scope ('full YAML text by id'). It also distinguishes from sibling tools by pointing to skflow_agents_list for available ids, making the tool's role clear.

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 usage context: it tells the agent to use skflow_agents_list to get available ids before calling this tool. However, it doesn't explicitly state when not to use this tool or mention alternatives beyond the list tool, so it falls short of a perfect 5.

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