Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

get_rpc_status

Read-onlyIdempotent

Checks FreeCAD connection health, addon protocol version, process ID, and dispatch status so you can diagnose RPC availability before running modeling or tutoring actions.

Instructions

Check connection health, addon protocol version, FreeCAD PID, and dispatch status.

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_rpc_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered structurally. The description adds only the list of reported signals; it says nothing about failure modes (what it returns when FreeCAD is unreachable) or cost/latency of the probe.

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?

A single front-loaded sentence listing the four inspected signals with zero filler. Every clause maps to an actual piece of returned status information.

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?

With an output schema present, the description need not explain return values, and with annotations covering safety the remaining burden is light. It is essentially complete for a zero-argument diagnostic; only the trigger condition for calling it is left implicit.

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 takes zero parameters, so the schema carries no semantic burden and there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

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?

States a specific verb ("Check") and enumerates exactly what is inspected: connection health, addon protocol version, FreeCAD PID, and dispatch status. This distinguishes it in substance from siblings like get_undo_redo_status or get_selection, though it never names an alternative explicitly.

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 only implied: the enumeration of health/connection/dispatch fields signals a diagnostic role, typically before or after issuing commands. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g., "call after connecting").

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