Skip to main content
Glama

get_safety_policy

Read-onlyIdempotent

Read the printer safety policy—temperature ceilings, confirmation thresholds, motion/extrusion caps, read-only/printing flags, and risk tiers—to see why a command was refused.

Instructions

The safety envelope this MCP server is enforcing: temperature ceilings, confirmation thresholds, jog/extrude caps, read-only and during-print flags, and which risk tiers require confirmation. Read this to understand why a call was refused.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint/idempotentHint/non-destructive annotations already establish that this is a safe, side-effect-free read, so the description does not need to argue safety. It adds useful behavioral context by revealing that the server enforces ceilings, confirmation thresholds and risk tiers — constraints that govern other tools' outcomes. It does not describe freshness, caching, or whether the policy can change at runtime, keeping it at a solid but not rich 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool exposes, followed by the reason to call it. The content list is dense but every item (thresholds, caps, flags, risk tiers) is substantive rather than 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?

An output schema exists, so return-value structure need not be explained, and the description still characterizes the returned policy's subject matter. For a zero-parameter, read-only introspection tool, an agent has everything needed to decide to call it and interpret the result.

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 input schema has zero properties, so there are no parameters whose meaning could be lost; baseline 4 applies. The description correctly implies a no-argument call by never referencing inputs and instead describing what the returned policy covers.

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 names the specific resource (the server's safety envelope) and enumerates its contents: temperature ceilings, confirmation thresholds, jog/extrude caps, read-only and during-print flags, and risk tiers. There is no verb-led phrasing ('returns'/'reads'), but the resource is unambiguous and no sibling tool returns policy data, so confusion with the many action tools is unlikely.

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?

It gives a concrete trigger: 'Read this to understand why a call was refused.' That is clear usage context absent from the schema or annotations. It does not add a proactive case (e.g., check before attempting risky moves) or state that no alternative tool provides this information, so it falls short of full when/when-not 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