Skip to main content
Glama

Tetrees AI

Accept AI Pack growth

accept_ai_pack_growth

Normalize a proposed delta with Tetrees Agent or provider-free portable normalization, run the deterministic growth gate, and append it to this owner only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequenceYes
productIdYesTetrees AI Pack product id
confirmationYes
normalizationNotetrees

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

D1.6/5.0
Behavior2/5

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

The phrase 'append it to this owner only' hints at a non-destructive mutation, but the description does not explain side effects, whether the action is reversible, or what happens if the confirmation constant is not provided. The annotation says destructiveHint=false, but the description itself does not clarify behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is dense and confusing, mixing jargon like 'provider-free portable normalization' with 'deterministic growth gate'. It is not concise or clear, and key information is buried.

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

Completeness1/5

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

There is no output schema and no explanation of return values, errors, or required confirmation behavior. Given the complexity of the operation and the many related tools, the description is far from complete for an agent to invoke it correctly.

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

Parameters1/5

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

Only productId is described, and its description merely repeats the parameter name. sequence, confirmation, and normalization have no meaningful explanation in the schema or description, and the enum values 'tetrees' and 'portable' are unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses vague terms like 'normalize', 'deterministic growth gate', and 'append it' without explicitly saying this tool accepts a proposed growth. It does not clearly distinguish the action from related tools like select_ai_pack_growth_version or propose_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 Guidelines1/5

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

No guidance is given about when to use this tool versus the many sibling tools. There is no mention of prerequisites, such as having a proposal or needing confirmation, nor any indication of when this tool should be chosen over alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation4/5

Most tools are clearly distinct by action and resource, though several clusters (accept/propose/select/list growth, prepare/execute/run) require careful reading of descriptions to avoid confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern, with clear action prefixes and descriptive resource nouns.

Tool Count2/5

With 26 tools, the set exceeds the recommended range and feels heavy, even though the domain covers publishing, runtime, growth, and reporting workflows.

Completeness4/5

The toolkit covers the main AI pack lifecycle—authoring, publishing, acquisition, running, searching, and reporting—but lacks explicit delete/revoke operations for drafts or entitlements.

Resources