Tetrees AI

Official

Overview Schema Source Related Servers Discussions Admin

List owned Tetrees AI Packs

list_owned_ai_packs

See which AI packs are available to you by listing purchased, claimed-free, and seller-owned packs tied to your account.

Instructions

List purchased, claimed-free, and seller-owned packs available to this account.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates a read-style list operation and scopes the result set, but it does not mention ordering, pagination, completeness guarantees, or what happens if no packs are owned. This is adequate but not detailed.

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?

A single, well-structured sentence with no filler. The core action and scope are front-loaded, and every word contributes to understanding the tool's purpose.

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 zero-parameter list tool, the description is largely complete: it identifies the resource and the ownership categories. There is no output schema, so a small note about the expected return shape (e.g., a list of pack IDs/metadata) would improve completeness, but it is not strictly necessary for a simple list operation.

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?

The tool has no parameters, so the baseline is 4. The description still adds useful semantic context by defining exactly what kind of packs are included, which helps the agent understand the implicit result filtering even without an input 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?

The description clearly identifies the action ('List') and the resource ('owned Tetrees AI Packs'), and specifies three meaningful ownership categories: purchased, claimed-free, and seller-owned. This distinguishes it from sibling search/list tools like search_ai_packs and list_ai_pack_growth.

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 conveys the intended use case: retrieving packs available to the current account. It does not explicitly mention when not to use this tool or name alternatives, but the ownership scoping and zero-parameter interface make the context clear enough for simple selection decisions.

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