Skip to main content
Glama
SoseiUncle

fcoh

by SoseiUncle

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fcoh_capabilitiesA

Report supported FCOH steps and actual CAD adapter readiness.

fcoh_validateA

Validate a project-relative .fcoh.yaml file without creating a CAD document.

fcoh_buildA

Create a NEW part under outputs/. cad: freecad or fusion. Fusion is asynchronous; use fcoh_status.

fcoh_statusB

Read CAD generation status, measured geometry, and exported artifact paths.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct function: capabilities reports environment, validate checks config, build initiates creation, status tracks progress. No overlapping purposes or ambiguous boundaries.

Naming Consistency5/5

All tools follow a consistent 'fcoh_<verb>' pattern, making the API predictable and easy to navigate. The verb choice clearly indicates the operation.

Tool Count5/5

Four tools is well-scoped for a focused CAD generation pipeline—enough to cover the essential steps without redundancy or bloat.

Completeness4/5

The set covers the core workflow: capability check, validation, build, and status. Minor gaps like cancellation or listing are absent, but the primary lifecycle is complete for a simple create-and-monitor use case.

Maintenance

ActivityMaintained
ResponsivenessNo issues