Skip to main content
Glama
Sign In
tua

tua

by Tuacircles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Velg hvor Tua-arkivet skal ligge

tua_setup
Idempotent

Configure the initial storage location for your Tua archive by selecting a cloud service or local folder, and save the setting for future use.

Instructions

Første kjøring: velg mappa arkivet skal ligge i — iCloud Drive, Dropbox, OneDrive, Google Drive eller lokalt — eller en egen sti. Kall dette BARE etter at brukeren selv har valgt (svar på en «oppsett:»-linje); gjett aldri. Uten argumenter: viser stedene som finnes på maskinen og hva som er valgt. Valget lagres i ~/.tua/config.json og kan endres senere (innstillinger, M15). Mappa «Tua» lages med et velkomstatom og Innboks.

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

Input Schema

NameRequiredDescriptionDefault
stiNoAlternativt: absolutt sti til en mappe som skal være arkivet.
stedNoSkytjeneste eller lokalt (~/Tua).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

With annotations declaring a non-read-only, non-destructive, idempotent write, the description adds real context: the selection is persisted to ~/.tua/config.json, and a «Tua» folder is created containing a welcome atom and an Inbox. It does not say what happens when re-run or whether an existing archive is touched, which is the only meaningful gap.

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?

Front-loads the primary action, then the critical constraint (never guess), then the no-argument behavior, then persistence details. Every clause carries information; nothing is filler.

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?

For a two-parameter, zero-required setup tool with no output schema, the agent has everything it needs: when to invoke it, what each argument selects, the no-argument fallback, side effects, and where state is stored.

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 both sti and sted are already fully documented, including the enum values and the absolute-path constraint. The description restates the same set of locations and the custom-path alternative but adds no format or precedence rules beyond it, so the baseline 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?

States a specific action (choose/create the archive folder) with exact scope: first run, five named backends or a custom path. It is clearly distinguishable from siblings like tua_save or tua_import, which operate on the archive rather than configuring it.

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?

Explicit when-to-use with an exclusion: call ONLY after the user has chosen (an answer to an «oppsett:»-line), never guess. It also documents the zero-argument mode (list existing locations and current selection) and notes the choice can be changed later via settings, covering the main alternative path.

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

Deploy Server

Other Tools