Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_list_app_store

List all available apps from the Technitium DNS app store, including versions and descriptions.

Instructions

List all available apps from the Technitium DNS app store with versions and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for dns_list_app_store tool that calls /api/apps/listStoreApps and returns the result as JSON.
    handler: async () => {
      const data = await client.callOrThrow("/api/apps/listStoreApps");
      return JSON.stringify(data, null, 2);
    },
  • Schema/definition for dns_list_app_store tool with name, description, and empty inputSchema (no parameters required).
    {
      definition: {
        name: "dns_list_app_store",
        description:
          "List all available apps from the Technitium DNS app store with versions and descriptions.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
  • Registration: appTools is spread into the getAllTools array, which includes dns_list_app_store.
    export function getAllTools(client: TechnitiumClient): ToolEntry[] {
      return [
        ...dashboardTools(client),
        ...dnsClientTools(client),
        ...zoneTools(client),
        ...recordTools(client),
        ...blockingTools(client),
        ...cacheTools(client),
        ...settingsTools(client),
        ...logTools(client),
        ...appTools(client),
        ...dnssecTools(client),
      ];
  • ToolEntry interface that defines the shape of tool objects including the dns_list_app_store entry.
    export interface ToolEntry {
      definition: ToolDefinition;
      handler: ToolHandler;
      readonly: boolean;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it correctly states the action (listing) and output content, it offers no additional behavioral context such as side effects, authentication requirements, or rate limits. For a straightforward read-only operation, this minimal disclosure is acceptable but not exceptional.

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?

The description is a single, concise sentence that directly communicates the tool's purpose. It is front-loaded with the primary action and resource, containing no extraneous information. Every word earns its place.

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?

Given the tool has zero parameters, no output schema, and a simple job, the description is complete. It specifies what the tool lists (available apps from the app store) and what details are included (versions and descriptions). No additional context is necessary for correct invocation.

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?

There are no parameters, so schema coverage is 100%. The description adds no parameter-specific information, which is appropriate given the absence of parameters. According to guidelines, a baseline of 4 is set for zero-parameter tools.

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 clearly specifies the action (list), resource (available apps from Technitium DNS app store), and the information provided (versions and descriptions). It effectively distinguishes itself from sibling tools like 'dns_list_apps' by clarifying the source (app store) and the status of apps (available, not installed).

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 description implicitly indicates when to use this tool: to browse available apps before installation. However, it does not explicitly specify when not to use it or mention alternatives like 'dns_list_apps' for installed apps. For such a simple tool, the implicit guidance is adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rosschurchill/technitium-mcp-secure'

If you have feedback or need assistance with the MCP directory API, please join our Discord server