Skip to main content
Glama
Sign In
Puppet Master

Puppet Master

by khr898
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

puppet_status

Verify local Flint model health and token budgets before delegating tasks to prevent failed or over-budget runs.

Instructions

Health and budgets of the local Flint model. Call once per session before delegating.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read-only probe and adds the once-per-session cadence, but says nothing about what happens when health is poor, whether it mutates state, or how budget data is surfaced.

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?

Two short sentences with zero waste, and the what-it-is statement is front-loaded ahead of the usage instruction.

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?

For a zero-parameter local status probe with no output schema, the description covers what it reports and when to call it. The shape of 'health and budgets' is left undefined, which is the only real gap.

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 baseline of 4 applies; there is nothing for the description to disambiguate.

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?

Names the resource (the local Flint model) and the attributes it reports (health and budgets), so the agent knows this is a status/inspection call. It doesn't explicitly contrast with siblings like puppet_check, but the name plus description make the intent unambiguous.

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?

"Call once per session before delegating" gives concrete timing and a de-duplication rule, which is exactly the kind of guidance agents need. It doesn't name what to call instead if the check fails, so no explicit alternatives are given.

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