Skip to main content
Glama

How Ridekick works

how_ridekick_works
Read-only

Explains what Ridekick does, what dealerships see, how prices work, what to tell a buyer when Ridekick isn't connected, is disconnected or stops working, and the rules for using Ridekick's tools. It needs no sign-in and reads nothing about the buyer. It answers questions about how Ridekick works and about a tool that stops working. It is not needed before you search, preview or send a request: those tools return a message for the buyer when they refuse. In every Ridekick answer, buyerLine is the sentence for the buyer, as Ridekick wrote it. A label that starts with "Test:" is a test row, and none of it is real. Unless a tool says otherwise, id is the id of a request from requests_list, and rowKey is the row key of one dealership from requests_get.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, and the description adds real context on top: no sign-in is required and it reads nothing about the buyer, which is the privacy guarantee an agent needs before calling it. It also documents cross-cutting conventions (buyerLine is the buyer-facing sentence, a "Test:" label marks fake rows, id refers to a requests_list request, rowKey to a requests_get dealership). These are behavioral facts not present in any structured field, though they describe other tools' outputs more than this tool's own return.

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 opening sentence is a long run-on, and the phrase about Ridekick being 'not connected, is disconnected or stops working' repeats the same condition three ways. The naming-convention block is dense and slightly compressed relative to its importance. It is informative but not tight.

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 zero-parameter help tool with no output schema, the definition covers what it documents, that no auth or buyer data is involved, and how to read the answers it and other tools produce. An agent has what it needs to decide whether to call it, though a note on the shape of the returned documentation would fully close the 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?

With zero parameters the baseline is 4, and nothing here contradicts that. The description does define the meaning of identifiers used elsewhere (id, rowKey) and the buyerLine convention, which helps an agent interpret results rather than invoke this call.

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 enumerates concrete topics the tool covers: what Ridekick does, what dealerships see, pricing, what to tell a buyer when Ridekick is offline or broken, and the rules for using the tools. That is more specific than the title, which merely restates the name. It stops short of a crisp one-line verb+resource statement because the coverage list is long and the opening clause is somewhat tautological.

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 states the use case (questions about how Ridekick works, or about a tool that stops working) and an explicit exclusion: it is not needed before search, preview, or send, because those tools return a buyer message on refusal. That exclusion is genuinely useful routing guidance. There is no named alternative for the documentation role itself, but none of the sibling names suggests one exists.

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