Skip to main content
Glama
alexar76

aimarket-mcp-packager

by alexar76
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

package_capability

Package a capability as a standalone MCP server. Generates Docker image, MCP manifest, pricing tiers, and connection string for easy deployment.

Instructions

Build a complete self-hosted MCP server package for an AIMarket capability.

Use this first. It assembles everything needed to ship the capability as a standalone MCP server: the Docker image name, the MCP manifest (server + tool definition), subscription/pricing tiers, and a connection string.

Returns: A JSON object (string) with keys: - docker_image: the image name to build/run. - mcp_manifest: the full MCP manifest (server metadata + tools). - subscription_tiers: pricing tiers derived for the capability. - connection_string: how a client connects to the running server.

Example: package_capability( capability_id="translate.multi@v2", product_id="prod-translate", name="Lyra Translator", description="Translate text into multiple languages.", input_schema={"type": "object", "properties": {"text": {"type": "string"}}, "required": ["text"]}, )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable display name for the packaged MCP server, shown to end users in MCP clients such as Claude Desktop (e.g. 'Lyra Translator').
registryNoContainer registry namespace for the built image. Defaults to 'aifactory'. Set your own org/namespace to publish under a different account (e.g. 'ghcr.io/acme').aifactory
product_idYesOwning product ID on the AIMarket hub, e.g. 'prod-translate'. Used to namespace the Docker image and the MCP manifest.
descriptionNoOne- or two-sentence summary of what the capability does. Surfaced in the MCP manifest and the Claude Desktop config. Optional but strongly recommended — it becomes the tool description in the generated server.
input_schemaNoJSON Schema object describing the capability's input. For example, an object with a required string property 'text'. Omit or pass null for a schema-less capability.
capability_idYesFully-qualified capability identifier to package, e.g. 'translate.multi@v2'. This is the single capability the generated MCP server will expose as a tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations provided, so the description carries full burden. It details return values (a JSON object with four keys) and provides an example. It does not mention side effects or destructive actions, but the tool appears to be a pure builder function without harmful consequences.

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 concise (three short paragraphs and an example), front-loaded with the main purpose, and structured with clear sections for returns and example. Every sentence adds value.

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?

Given that an output schema exists (inferred from context), the description adequately explains the return structure. It covers all necessary aspects: parameter details, return format, and usage ordering relative to siblings.

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 100%, but the description adds significant value beyond schema: it explains the purpose of each parameter in context (e.g., 'the single capability the generated MCP server will expose as a tool' for capability_id) and includes a comprehensive 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 its purpose: 'Build a complete self-hosted MCP server package for an AIMarket capability.' It uses a specific verb ('Build') and resource ('self-hosted MCP server package'), and distinguishes from siblings by noting 'Use this first' and that it assembles everything needed.

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 explicitly says 'Use this first,' providing clear context for when to use it. It does not mention when not to use it or alternatives, but siblings are sufficiently different so no confusion arises.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexar76/aimarket-plugins'

If you have feedback or need assistance with the MCP directory API, please join our Discord server