Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

log_status

Displays a status message in Houdini's status bar so MCP clients can report progress, results, or warnings during command execution.

Instructions

Display a status message in Houdini's status bar.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "log_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
severityNomessage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a transient, non-destructive UI write, but never states whether the message persists, is overwritten by later calls, is visible to the user only, or has side effects. For a UI-affecting tool with zero annotation coverage this leaves meaningful gaps.

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?

One short sentence with the purpose front-loaded and no wasted words. It is efficient, though the brevity is part of why the semantics are thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A two-parameter tool is simple, but with no annotations, no output schema, and 0% schema coverage, the description should at least explain the severity options and the transient nature of the status bar message. Neither is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only implies that the string is the status text; the `severity` parameter is never mentioned, and its default of "message" suggests an unstated set of accepted values that the agent cannot discover from either source.

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?

"Display a status message in Houdini's status bar" gives a clear verb (display) and target surface (status bar), which is distinct from the node-building and cooking siblings. It stops short of explicitly differentiating itself from any named alternative, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus other feedback mechanisms, no mention of whether it is user-facing only, and no exclusions. The agent must infer usage entirely from the one-line purpose.

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