Skip to main content
Glama
Sign In
wara

wara

by Hercast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

altium_status

Read-only

Reports server mode, Altium version, open project, and any problems, even when Altium is closed, so you can see what to fix.

Instructions

Report server mode (read_only, read_write or read_write_save), Altium version, the open project and any problems. The only tool that works when Altium is closed; it says what to fix.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already communicate readOnlyHint=true, so the safety bar is lower. The description adds a meaningful behavioral trait beyond annotations: it works even when Altium is closed and reports problems with actionable guidance. It does not cover auth or rate limits, but those are not essential here.

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?

Two sentences, each earning its place. The returned data is front-loaded, followed immediately by the key differentiator and diagnostic value. There is no 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 parameterless, read-only status tool with an output schema available, the description supplies everything an agent needs: what it reports, when it works, and that it surfaces problems to fix. No additional context is required to invoke it correctly.

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?

The tool has zero parameters, which establishes a baseline of 4. The description does not need to explain parameter semantics, and no parameter information is missing or misleading.

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 uses a specific verb ('Report') and enumerates the exact resources returned: server mode, Altium version, open project, and problems. It also distinguishes itself from all siblings by stating it is 'The only tool that works when Altium is closed,' so an agent can identify it without reading the schema.

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 clearly implies the primary usage context: diagnostics when Altium is closed or when something is wrong ('says what to fix'). It does not explicitly state when not to use it or name a specific alternative for open-server scenarios, but the conditional differentiator provides strong guidance.

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