Skip to main content
Glama

ADITUS Developer Portal MCP

Get an integration guide

get_guide
Read-onlyIdempotent

Markdown of an integration guide. 'micro-frontend' is the compact Shop Micro Frontend contract for coding agents (mounting, sessions, styling, Web Component, lifecycle, security); 'micro-frontend-docs' is the complete Micro Frontend documentation as on the website; 'micro-frontend-overview' is the non-technical overview (what it is, purchase flow, base setup, add-on levels); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section.

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

Input Schema

NameRequiredDescriptionDefault
guideYesGuide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', 'guidelines', 'webhooks'
sectionNoOptional section heading (or slug) to return only that part

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / guide / description
      Previous value: -"Guide id, e.g. 'micro-frontend', 'guidelines', 'webhooks'"New value: +"Guide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', 'guidelines', 'webhooks'"
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the response is Markdown, module guides originate from the API reference, and passing a section heading narrows the response to that part. It omits what happens when a guide or section is not found.

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?

It leads with what the tool returns, then spends the rest on value selection and section filtering, so the important parts are front-loaded. The semicolon-chained enumeration is dense but each clause carries a distinct guide definition rather than filler.

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 only two parameters, no output schema, and full annotation coverage, the definition covers what an agent needs: output format, valid guide families, and section scoping. The only gaps are behavior on invalid guide ids or unmatched section headings and any size/truncation limits on large guides.

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% and both parameters carry their own descriptions with examples, which sets the baseline at 3. The description exceeds that by explaining the semantic content of each guide id (scope, audience, source), information the schema does not convey, and it reinforces that 'section' returns only that part.

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 names the resource (an integration guide) and its return format (Markdown), then enumerates distinct guide categories with what each contains, which lets an agent pick the right document without opening anything else. It stops short of naming sibling tools like search_docs or list_modules, so the boundary against those is left implicit.

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?

It gives concrete selection guidance across guide values: 'micro-frontend' for the compact coding-agent contract, 'micro-frontend-docs' for full website docs, 'micro-frontend-overview' for non-technical content, and module guides such as 'guidelines' or 'webhooks' from the API reference. It does not state when to prefer this over search_docs or list_modules, so there are no explicit exclusions among siblings.

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.

Resources