Skip to main content
Glama

Get Install Instructions

get_install_instructions
Read-onlyIdempotent

Return install instructions for the saved checkout path, or a no-code handoff for promo-code-only setup. When no path is saved, Payment Links is the default recommendation.

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_install_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional path override. Defaults to the saved account setup path, or payment_links when none is saved.

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / path / description
      Previous value: -"Install path. Defaults to payment_links."New value: +"Optional path override. Defaults to the saved account setup path, or payment_links when none is saved."
    • changedInput schema / properties / path / enum
      Previous value: -[
      -  "payment_links",
      -  "embedded_stripe",
      -  "custom_checkout_sessions"
      -]New value: +[
      +  "payment_links",
      +  "embedded_stripe",
      +  "custom_checkout_sessions",
      +  "promo_codes"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral value by disclosing that output is conditional: instructions per saved path versus a no-code handoff for promo-code-only setups, and a default fallback when nothing is saved.

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?

Two front-loaded sentences with no filler. The default-Payment-Links sentence mildly repeats the schema's own default note, a small redundancy, but nothing else 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?

With an output schema present, return values need not be explained, and annotations cover safety. A single optional parameter plus the conditional-output explanation makes this sufficient, though a note on how the saved path is set or reset would complete it.

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 the enum is documented, so baseline is 3. The description adds meaning beyond the schema by explaining that the promo_codes path yields a no-code handoff rather than install instructions, which tells the agent the outcome differs per enum value.

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 (return install instructions) scoped to the saved checkout path, plus the alternate no-code handoff outcome. It does not explicitly distinguish itself from near neighbors like get_setup_context or read_setup_status, so an agent must infer the boundary.

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 gives one concrete usage rule — Payment Links is the default when no path is saved — and implies the path parameter is an optional override. It never says when to call this instead of get_setup_context or read_setup_status, leaving the sibling choice implied rather than stated.

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