Skip to main content
Glama

Get maintenance plan and financing

get_membership_and_financing
Read-onlyIdempotent

AtlantFlow's maintenance plan (single plan, $200/year per system, two visits a year), the single-visit tune-up ($149), and financing (from $89/month, $0 down on approved credit), plus the warranty rules.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 safety and idempotency are covered structurally. The description adds concrete business facts (plan price, visit frequency, financing floor, $0 down subject to credit) that help the agent know what content to expect, but says nothing about whether these figures are static or time-sensitive, nor what form the response takes. With annotations carrying the safety profile, this is a moderate contribution rather than a rich one.

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?

A single sentence with no filler, front-loaded on the maintenance plan. The nested parenthetical price list is dense but every clause maps to a retrievable fact category, so nothing is wasted.

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, read-only lookup with full annotation coverage and no output schema, the definition covers all the content categories an agent would need to know exist. The remaining gap is that with no output schema the description could hint at how the plan/financing/warranty information is structured in the response.

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, so there is no argument meaning to add; the baseline of 4 applies. The description correctly implies no input is required by simply stating the retrievable content.

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 exactly what this tool returns: the single maintenance plan ($200/year per system, two visits/year), the $149 tune-up, financing from $89/month, and warranty rules. That is a specific resource, though the verb is only implied by the name and it does not distinguish itself from sibling pricing tools such as get_pricing that likely also expose the tune-up price.

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?

Usage is only implied by the content list – an agent can infer this answers questions about plans, tune-ups, financing, or warranty terms. There is no explicit when-to-use statement and no routing advice relative to get_pricing or get_services, which are the obvious overlapping 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