Skip to main content
Glama
Sign In
Medusa.js Documentation MCP Server

Medusa.js Documentation MCP Server

by Alexcs24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_sections

Retrieve all available documentation sections. Optionally filter by category to narrow results.

Instructions

List all available documentation sections

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

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter sections by category (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states 'List all...'. It fails to mention that the operation is read-only, any authentication requirements, potential side effects, or whether results are paginated. This is insufficient for safe invocation.

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?

Description is a single, direct sentence with no wasted words. It is front-loaded and immediately actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the core purpose is covered, the description omits details about the output format, ordering, pagination, or how this listing interacts with sibling tools. For a simple tool this may suffice, but more context would improve reliability.

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?

The input schema fully describes the single parameter 'category' with a clear description. The tool description adds nothing beyond what the schema provides, earning the baseline score for high schema coverage.

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?

Description explicitly states 'List all available documentation sections' – a clear verb+resource combination. The tool name 'list_sections' is distinct from siblings 'get_section' (single section) and 'search_docs' (keyword search), making the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_section or search_docs. The agent must infer from tool names only; explicit advice on use cases or exclusions is missing.

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