agent-pool-mcp

Overview Schema Source Related Servers Discussions Admin

get_skill_content

Retrieve the full markdown content and metadata of a specific workspace or global skill, identified by name, for atomic loading after context resolution.

Instructions

Return one global or active workspace skill with metadata and markdown content. Use after resolve_context returns a skill item that needs atomic loading.

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

Input Schema

Name	Required	Description
`cwd`	No	Project directory. Defaults to current working directory.
`name`	No	Skill name returned by list_skills or resolve_context items.
`files`	No	Known relevant file paths used to activate workspace context when loading this item.
`skill_name`	No	Alias for name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.3Jul 29, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided. Description only mentions return content; fails to disclose error behavior, permission requirements, or side effects of loading. As a read tool, safety is implied but not explicit.

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?

Single sentence stating purpose and usage context. No wasted words, front-loaded with key action and resource.

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?

Given no output schema, description mentions return includes metadata and markdown content. Usage guidance ties to resolve_context. Could elaborate on error handling but sufficient for the tool's simplicity.

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 covers 100% of parameters with descriptions. The tool description adds context about using after resolve_context, but this is also hinted in the name parameter description. Adds marginal value beyond schema.

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 verb 'Return' and resource 'one global or active workspace skill with metadata and markdown content'. Distinguishes from list_skills by specifying atomic loading of a single item.

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 to use after resolve_context returns a skill item needing atomic loading. Provides clear context for invocation but does not explicitly list when not to use or alternatives.

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