Skip to main content
Glama

Install

install
Read-onlyIdempotent

Return install commands for the open-source package (pip install hefesto-ai, Python 3.11+). 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 {}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
stepsYesQuickstart steps, in order.
commandYespip install command.
requiresYesPython version required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties
      Removed value: -{}
    • removedInput schema / required
      Removed value: -[]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds a genuinely valuable clarification beyond them: 'Does not install anything on the caller's machine,' which defuses the misleading verb 'install' — a real risk of misinvocation.

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, each doing distinct work: what it returns, when to use it, and the critical non-effect. Front-loaded and waste-free.

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-format explanation is unnecessary. For a zero-parameter, non-mutating helper, the description covers everything an agent needs to decide and invoke correctly.

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. The description confirms the calling convention explicitly ('No parameters: call it with {}'), which is helpful even though the empty schema already implies it.

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 a named package with an explicit version requirement (Python 3.11+) — and the sibling set (analyze/compare/pricing) makes the distinction obvious. An agent can tell exactly what it gets back.

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 trigger conditions: 'when the user wants to run HefestoAI locally, in a pre-commit hook or on a whole repository.' No explicit when-not or named alternatives, but the trigger context is clear and the siblings are unrelated enough that no routing note is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.