Skip to main content
Glama
Sign In
grimoire

grimoire

by PentHertz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

grimoire_env

Determine the runtime environment's container, OS, package manager, and sudo availability to decide how to install tools.

Instructions

Detect the runtime environment: whether this is an RF-Swift container, the OS and package manager, whether RF-Swift install scripts are reachable, and root/sudo availability. Use this to decide how to install tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It explains what is detected but does not mention potential side effects (likely none), required permissions, or that it is a read-only operation. Provides sufficient but not exhaustive transparency.

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?

The description is two sentences with no unnecessary words. It front-loads the purpose and ends with usage guidance, efficiently conveying all necessary information.

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?

Given no output schema, the description lists the detected items (container, OS, etc.) but does not explicitly state the return format (e.g., JSON keys). For a simple detection tool, this is nearly complete, as the agent can infer structure from the listed attributes.

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

Parameters5/5

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

The input schema has zero parameters (empty object), so schema coverage is 100%. The description adds no parameter info (none needed) but lists the detected environment attributes, effectively describing the output.

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?

The description clearly states the tool detects runtime environment details (container, OS, package manager, install script reachability, root/sudo availability) and its purpose is to inform installation decisions, distinguishing it from sibling tools like grimoire_which.

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?

The description explicitly says 'Use this to decide how to install tools', providing clear context. It doesn't state when not to use or list alternatives, but it effectively guides the agent towards usage before installation tasks.

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