Tetrees AI

Official

Overview Schema Source Related Servers Discussions Admin

Download an owned Tetrees AI Pack

download_ai_pack

Obtain a short-lived, entitlement-gated URL to download a signed TAIP envelope. Verify access rights and retrieve the AI pack securely.

Instructions

Return a short-lived entitlement-gated URL for the signed .taip envelope.

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": {
      "productId": "<productId>"
    },
    "name": "download_ai_pack"
  }
}

Input Schema

Name	Required	Description	Default
`productId`	Yes	Tetrees AI Pack product id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose key behavior: it returns a short-lived, entitlement-gated URL rather than the file directly. This is meaningful context that helps the agent understand side effects and constraints.

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 tightly-worded sentence with no filler. Every qualifier—short-lived, entitlement-gated, signed .taip envelope—carries useful information and is front-loaded.

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 required parameter and no output schema, the description gives the essential information: the result is a URL, it is short-lived, and entitlement is required. It is slightly terse about prerequisites or error conditions, but adequate 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 description coverage is 100%, so the single productId parameter is already fully documented in the schema. The description adds no parameter-specific meaning beyond the schema, which matches the baseline for high coverage.

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 a specific action: returning an entitlement-gated URL for the signed .taip envelope, and the title further clarifies it downloads an owned Tetrees AI Pack. This distinguishes it from sibling tools like list_owned_ai_packs or run_ai_pack.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given for when to use this tool versus alternatives. The description implies downloading is the use case, but it does not mention conditions, exclusions, or how it relates to siblings such as list_owned_ai_packs or get_ai_pack_runtime_profile.

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