Skip to main content
Glama

Search Axons Mobility help

search_help
Read-onlyIdempotent

Search Axons Mobility's public knowledge base. Axons Mobility is AI fleet management software for golf carts, for golf cart OEMs, dealers and fleet operators (resorts, golf courses, communities and rental businesses): an operator console, a branded rider app, Intelligence, an AI assistant and MCP access. Covers pricing, the free trial and going live, supported vehicles and connected devices, integrations, safety checks, payments, security and privacy, use cases, and how riders sign up, unlock, ride, pay and get support in an operator's app. Ask in plain words. The best match comes back in full; other matches as an excerpt you can open with read_help_page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pages to return. Default 3.
audienceNovisitor = someone looking at Axons Mobility as a product (buyers, partners, press); rider = someone using an operator's branded ride app. Omit to search both.
questionYesThe question in plain words, e.g. 'how much does it cost' or 'how do I end my ride'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuinely non-obvious return behavior: the best match is returned in full while other matches come back as excerpts opened via read_help_page, which tells the agent how to chain calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the middle sentence is a product-marketing blurb ('an operator console, a branded rider app, Intelligence, an AI assistant and MCP access') that does not help the agent invoke this tool. The long topic enumeration earns some of its space for retrieval matching, but the product pitch does not.

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 carries the burden of describing results, and it does so reasonably well (full top match plus excerpts). Combined with the domain scoping and audience guidance it is sufficient to call correctly, though pagination and match-scoring behavior remain unstated.

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%, so all three parameters are already documented in the schema, including the audience enum and limit default. The description adds only the 'plain words' phrasing hint, which duplicates the schema's own example; baseline 3 applies.

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?

Opens with a specific verb+resource ('Search Axons Mobility's public knowledge base') and immediately scopes the domain (AI fleet management for golf carts) so an agent can tell it isn't a general web search. It also names the follow-up sibling ('open with read_help_page'), routing the agent past ambiguity.

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?

It implies usage by enumerating the topics covered and telling the caller to 'ask in plain words', which helps an agent decide the corpus is relevant. But it never states when to use this versus the sibling list_help_topics, nor any exclusions, so the browse-vs-search decision is left to inference.

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