HefestoAI

Install

install

Read-onlyIdempotent

Return install commands for the open-source package (pip install hefesto-ai, Python 3.10+). Use it when the user wants to run HefestoAI locally, in a pre-commit hook or on a whole repository. Does not install anything on the caller's machine. No parameters: call it with {}.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`steps`	Yes	Quickstart steps, in order.
`command`	Yes	pip install command.
`requires`	Yes	Python version required.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "Install commands for the open-source package. Does not install anything. The content text is the same prose as before.",
+  "properties": {
+    "command": {
+      "description": "pip install command.",
+      "type": "string"
+    },
+    "requires": {
+      "description": "Python version required.",
+      "type": "string"
+    },
+    "steps": {
+      "description": "Quickstart steps, in order.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "command",
+    "requires",
+    "steps"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties
```
Removed value: -{}
```
- removedInput schema / required
```
Removed value: -[]
```
First observedFeb 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant context the annotations cannot express: it only returns commands and 'Does not install anything on the caller's machine' — a critical clarification that prevents an agent from reporting a completed install. It omits any mention of what the returned command set contains, but the output schema covers return structure.

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?

Three short sentences, front-loaded with purpose and the actual command, then usage, then the key non-effect caveat. Nothing is padded or repeated.

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?

For a zero-parameter, read-only tool with a declared output schema, the description covers everything an agent needs: what it returns, when to reach for it, that it performs no installation, and how to call it.

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?

Zero parameters, so the baseline is 4, and the description reinforces the empty-object contract explicitly with 'No parameters: call it with {}', which removes any chance of an agent inventing arguments despite additionalProperties=false.

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

Purpose5/5

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

States a specific verb and resource — 'Return install commands for the open-source package' — and even names the concrete command (pip install hefesto-ai) and required runtime (Python 3.10+). This is unmistakably different from the sibling tools analyze, compare and pricing, which an agent can tell apart without opening any schema.

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?

Gives concrete invocation contexts: run HefestoAI locally, in a pre-commit hook, or on a whole repository. It does not name a sibling as an alternative or state when NOT to use it, but the usage envelope is clear enough that mis-selection against analyze/compare/pricing is unlikely.

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

All HefestoAI tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.