Skip to main content
Glama
Sign In
majrooo-mcp-devkit

majrooo-mcp-devkit

by Majrooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

help_tool

Read-onlyIdempotent

Retrieve detailed documentation for any MCP tool, including parameters, types, defaults, and descriptions. Use it to understand required inputs before calling a tool.

Instructions

Get detailed help for a specific MCP tool — parameters, types, defaults, description.

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

Input Schema

NameRequiredDescriptionDefault
toolYesTool name to get help for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful value by naming what is returned (parameters, types, defaults, description), which partially compensates for the absence of an output schema, but it says nothing about error behavior for unknown tool names.

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?

A single front-loaded sentence that conveys purpose and return contents with no filler. Every clause earns its place.

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?

For a one-parameter, read-only lookup tool, the definition is essentially complete, and it describes the return contents in the absence of an output schema. Minor gap: no mention of behavior when the requested tool does not exist.

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

Parameters3/5

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

Schema description coverage is 100% and the single 'tool' parameter is already documented as 'Tool name to get help for'. The description adds no syntax, format, or validity constraints beyond that, so the baseline 3 applies.

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?

The description states a specific verb ('Get') and resource ('detailed help for a specific MCP tool'), making the purpose unambiguous. It implicitly distinguishes itself from list_tools via the word 'specific', but does not name that sibling explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied: consult this when you need details about a particular tool. There is no explicit when-to-use vs. list_tools guidance or statement of prerequisites (e.g., that the tool name must be known/valid). Adequate but with a clear gap.

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