Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Get server info

get_server_info
Read-onlyIdempotent

Returns what the millwork-mcp-lite server does, its license, available tools and typical flow, plus what the full millwork-mcp version adds. Use it to check capabilities or find features outside the lite tools.

Instructions

What millwork-mcp-lite does, its license, and what the full millwork-mcp adds (CNC router nesting, woodWOP DXF output, 32mm joinery, grain matching, estimating, inventory).

Use when someone asks what this server can do, or needs something outside the lite tools. Takes no input.

Returns: {name, license, tools, typical_flow, full_version, full_version_adds, contact}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful context by enumerating which capabilities exist only in the full version (CNC nesting, woodWOP DXF, grain matching, estimating), which is behaviorally meaningful for deciding whether to escalate. It does not describe the typical_flow content it returns, but that is a minor omission.

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?

Three short, front-loaded blocks: purpose, usage, and return shape. The parenthetical feature list earns its space because it drives the escalate-to-full-version decision rather than padding.

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

Completeness4/5

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

Although no output schema exists, the description lists the returned fields (name, license, tools, typical_flow, full_version, full_version_adds, contact), which is enough for an agent to know what it gets. Complete for a trivial zero-parameter informational tool.

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 correctly reinforces this with 'Takes no input.' No further param semantics are needed or missing.

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 resource (this server's own metadata: purpose, license, and what the full millwork-mcp version adds) and clearly frames itself as meta-information rather than a woodworking computation. An agent can immediately distinguish it from domain siblings like build_cutlist or nest_sheets.

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 when-to-use guidance ('when someone asks what this server can do, or needs something outside the lite tools'), which also implicitly routes out-of-scope requests toward the full version. It states no input is required, removing any invocation ambiguity.

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