Skip to main content
Glama
Sign In

ihumane

by ai.ihumane
OverviewDiscussionsAdmin

Open an ihumane module

ihumane_module
Read-only

Opens any ihumane module before that part of the work: its workflow, its first step and the rules likely to matter for your task. ihumane_start tells you which modules apply. Modules: ihumane core: 'humans' (Working with your human). Design: 'ui-design' (UI design), 'ux-design' (UX design), 'graphics' (Graphics and images). Engineering: 'code-craft' (Code craft), 'front-end' (Front-end build), 'code-review' (Code review), 'qa-testing' (QA and testing). Product: 'product-thinking' (Product thinking). Writing: 'copy' (Copy and UX writing). Free: each module's start; the other rules are ihumane Pro and are named by title.

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": {
      "name": "<name>"
    },
    "name": "ihumane_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe module, e.g. 'qa-testing' or 'ux-design'
taskNoWhat you're about to do, in a sentence, e.g. 'test the new checkout before release'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description adds real behavioral detail: it discloses what payload to expect (workflow, first step, relevant rules) and the free/Pro split ('each module's start is free; the other rules are ihumane Pro and are named by title'). That gating disclosure is valuable context the annotations could not convey.

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?

Purpose and routing are front-loaded ahead of the module catalog, and every sentence carries information. The parenthetical glosses on each module name are somewhat repetitive of the enum ids and add bulk, though they stay organized.

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?

With no output schema, the description correctly explains what is returned and how access tiers affect content, and it covers the single required parameter's domain. Minor gaps remain around re-invocation behavior and whether modules persist across calls, but nothing essential to calling it is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description exceeds it by categorizing and glossing the enum values (Design, Engineering, Product, Writing groups) which helps an agent map a task domain to a module id. The optional 'task' parameter is left entirely to the schema, keeping this from a 5.

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 ('Opens any ihumane module') plus exactly what it returns ('its workflow, its first step and the rules likely to matter for your task'). It also distinguishes itself from a named sibling by saying 'ihumane_start tells you which modules apply', so an agent can separate routing from loading.

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 clear timing guidance ('before that part of the work') and points to the alternative tool that determines which module applies. It lacks an explicit negative case (e.g., do not call with a module already open, or re-calling behavior), so it falls short of full when/when-not coverage.

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

All ihumane toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources