Tetrees AI

Create Tetrees AI Pack draft

create_ai_pack_draft

Create an owner-bound AI Pack listing with the complete buyer guide and two concrete example uses. Accept current terms first. Free drafts do not require Stripe Connect.

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": {
      "name": "<name>",
      "description": "<description>",
      "category": "<category>",
      "capabilities": "<capabilities>",
      "models": "<models>",
      "listing": "<listing>"
    },
    "name": "create_ai_pack_draft"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`models`	Yes
`listing`	Yes
`category`	Yes
`priceUsd`	No
`description`	Yes
`capabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Discloses creation, owner-binding, and payment/terms conditions beyond the readOnly/destructive hints. Does not mention failure modes, validation, or success output, but enough for a create-draft operation.

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?

Two concise sentences with the main action first and conditions second; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex nested schema with no output schema, the description is too sparse. It omits parameter-level semantics, success/error behavior, and how the terms-acceptance prerequisite is enforced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has zero description coverage and nested listing fields, while the description only hints at 'buyer guide' and 'example uses'. It does not explain priceUsd, capabilities, models, or the nested listing properties.

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 it creates a draft AI Pack listing, with owner binding and required buyer guide/example uses. Distinguishes from sibling tools like update_ai_pack_draft and publish_ai_pack by using 'create' and 'draft'.

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 prerequisite guidance ('Accept current terms first') and a condition ('Free drafts do not require Stripe Connect'), but does not explicitly name alternatives such as update_ai_pack_draft or submit_ai_pack_for_audition.

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

All Tetrees AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?