Skip to main content
Glama
ALOC Model Context Protocol (MCP) Server

ALOC Model Context Protocol (MCP) Server

Official
by MaSSTeck

aloc_get_sitemap

Retrieve the complete ALOC developer portal sitemap with direct links to documentation and error code guides for navigation and troubleshooting.

Instructions

Get complete navigation sitemap and direct links to ALOC developer portal, documentation, and error code guides. Free (0 credits).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the zero-credit cost and the nature of the returned content (navigation links), which is useful context. It does not explicitly state that the call is read-only and side-effect free, nor whether the sitemap is static or changes between calls, so behavioral disclosure is moderate rather than complete.

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?

Two short sentences with no filler: the resource and its contents come first, and the cost qualifier follows. Every clause adds information an agent can act on.

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?

There is no output schema, so the description must convey return content, and it does so at a reasonable level (sitemap plus direct links to portal, docs, error guides). For a zero-parameter, zero-cost lookup tool this is close to sufficient, though a hint about the response shape (e.g. a link list) would close the remaining gap.

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?

The tool takes zero parameters and the schema is therefore fully covered; the description correctly implies no input is required. There is no parameter meaning to add, so the baseline 4 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?

States a specific verb and resource ('Get complete navigation sitemap') and clarifies the payload as direct links to the developer portal, documentation, and error code guides. It is distinguishable from siblings like aloc_get_platform_overview by its navigation/link-directory framing, though it does not name any sibling to sharpen the contrast.

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?

The 'Free (0 credits)' note gives an implicit reason to prefer this tool when an agent is cost-constrained or needs to locate docs, but there is no explicit when-to-use guidance and no statement of when another tool (e.g. aloc_get_platform_overview) would be a better choice. Usage must be inferred.

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