Skip to main content
Glama
Sign In
structuresynth-mcp

structuresynth-mcp

by Astrid3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engine_status

Checks whether the ssynthgen engine binary is available, reporting its path or install guidance when missing.

Instructions

Report the path of the ssynthgen engine binary, or install help if missing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool reports a path and may return install help if the binary is missing, which implies a read-only status check. It does not clarify permissions, whether it verifies existence, or platform/path caveats, so behavioral context is adequate but not rich.

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 wasted-free sentence that front-loads the primary action and appends the conditional fallback. It is appropriately sized for a simple status tool.

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?

The tool is simple, has no parameters, and has an output schema, so the description need not explain return values. It communicates the main outcome and missing-install fallback, though the phrase 'install help' remains slightly vague.

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, so there are no parameter semantics to explain. The baseline for zero-parameter tools is 4, and no additional parameter context is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it reports the path of the ssynthgen engine binary. It also states a conditional fallback behavior, install help if missing. It is clear without relying on the title, though it does not explicitly differentiate itself from the many rendering/preview siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied as a diagnostic check for the engine binary path or missing-install help. There is no explicit guidance on when to choose this over other tools or when not to use it, so it meets the minimum viable threshold but leaves selection mostly inferred.

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