Tetrees AI

Official

Overview Schema Source Related Servers Discussions Admin

Get private Agent AVCP feedback

get_ai_pack_private_report

Access owner-only AI pack report to identify failures and get recommended next actions, keeping sensitive insights private from buyers.

Instructions

Read actionable owner-only failures and next actions without exposing them to buyers.

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

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

A4.2/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 well: 'Read' signals a safe read operation, 'owner-only' discloses access scope, and 'without exposing them to buyers' describes a privacy behavior. It does not specify permissions, errors, or output formatting, but those are less critical for a one-parameter read tool.

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 sentence that front-loads the core purpose ('Read actionable owner-only failures and next actions') and appends the privacy qualifier. There is zero redundancy or filler.

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 simple one-parameter, read-only tool with no output schema, the description covers what is returned (failures and next actions), for whom (owner-only), and a key privacy constraint (not exposed to buyers). It could add an explicit cross-reference to get_ai_pack_report, but nothing essential is missing for selecting and invoking it.

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?

Input schema coverage is 100% and the only parameter productId already has schema documentation ('Tetrees AI Pack product id'). The description adds no additional parameter semantics, so the schema-carries-the-load baseline of 3 applies.

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 states a specific action ('Read'), a concrete resource (private Agent AVCP feedback), and a scope ('owner-only failures and next actions'). The phrase 'without exposing them to buyers' marks it as the private counterpart to buyer-facing report tools, so an agent can tell it apart from get_ai_pack_report.

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 'owner-only' wording and the 'without exposing them to buyers' qualifier give clear context that this is for the pack owner's private review rather than buyer-facing reporting. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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