Skip to main content
Glama
Sign In

AANet

by space.aanet
OverviewDiscussionsAdmin

aanet_create_trial_workspace

Create a free trial workspace — no payment, no arguments, works immediately. Use this instead of aanet_create_workspace when you want to exercise the API (files, locks, sub-keys, messages) before committing real money.

Pre-funded with a small fixed balance (currently 1000 units = $0.01 — enough
for a realistic multi-agent round, but NOT for a successful write of a
file at the 1 MiB cap, which costs 1029 units; that is a known limit of
the trial, not a bug. An oversize write is still rejected with 413 for
free, so the cap itself is checkable) and
expires exactly 24 hours after creation, regardless of remaining
balance or activity — it is then deleted permanently along with
everything in it. Returns the same shape as aanet_create_workspace plus
trial_expires_at. aanet_deposit and aanet_request_refund both reject a
trial workspace outright, since no real money ever entered it. If your
task won't fit in 24 hours, create a real workspace instead.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it does: exact pre-funded balance (1000 units), the 24-hour expiry independent of activity, permanent deletion of contents, rejection by aanet_deposit and aanet_request_refund, and even error behavior (413 on oversize writes). It also flags a known limitation rather than letting the agent infer a bug.

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

Conciseness4/5

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

Front-loaded with purpose, key property, and the sibling routing in the first two sentences, then the operational details. It is denser and longer than most, and the nested parenthetical about the 1 MiB write cost is somewhat convoluted, but nearly every clause conveys actionable information.

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

Completeness5/5

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

No output schema exists, yet the description explains the return shape ('same shape as aanet_create_workspace plus trial_expires_at') and covers cost, lifetime, deletion semantics, and which sibling tools will reject the workspace. Nothing an agent needs to call this correctly is missing.

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?

Zero parameters, so the baseline is 4. The description confirms 'no arguments', which matches the empty schema, but there is no additional parameter meaning to convey.

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?

States a specific verb and resource (create a free trial workspace) and immediately distinguishes it from the sibling aanet_create_workspace, which is named explicitly. An agent can identify the tool's role without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing: 'Use this instead of aanet_create_workspace when you want to exercise the API ... before committing real money', plus a clear when-not ('If your task won't fit in 24 hours, create a real workspace instead'). Both the selection condition and its boundary are stated.

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

All AANet toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources