Skip to main content
Glama

AvianSuite

by com.aviansuite
OverviewDiscussionsAdmin

Enable an app

enable_app
Idempotent

Use to turn on a built-in app for this workspace: magpie for bookkeeping, martin for CRM. It initializes the app in the workspace store and adds its tools (prefixed magpie_ or martin_) for every agent on the workspace. Enabling an app that is already on is safe. Some clients only pick up new tools after reconnecting. To turn the app off again, call disable_app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYesThe app to enable.
currencyNoMartin only: the workspace's three-letter ISO currency, fixed once set. Default USD.
workspaceNoOptional. The workspace to act on, as list_workspaces names it. Leave it out to use this connection's first workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "Optional. The workspace to act on, as list_workspaces names it. Leave it out to use this connection's first workspace.",
+  "type": "string"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing side effects: it initializes the app in the workspace store and registers tools (magpie_/martin_ prefixed) for every agent on the workspace, plus a client-reconnect caveat. Annotations only cover idempotency/safety, so this added context is genuinely valuable.

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 action and its targets, then adds behavior and the routing hint in tight sentences. Every sentence carries distinct, non-redundant 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?

For a 3-param mutation tool with no output schema, the description covers persistence, scope (all agents on the workspace), idempotency, client caveat, and the inverse operation. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the schema already documents app, currency, and workspace. The description adds only the magpie/martin tool-prefix convention, which is mildly useful but does not enrich parameter meaning beyond the enum and field descriptions.

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 (turn on) plus the resource (built-in app in this workspace) and enumerates the concrete values (magpie, martin). It clearly contrasts with the sibling disable_app, so an agent can distinguish them without opening either 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?

Explicitly names the alternative and the condition that selects it ('To turn the app off again, call disable_app'), and notes that re-enabling an already-on app is safe. Both the when and the when-not are stated.

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

All AvianSuite toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources