Skip to main content
Glama
Sign In

SatelliteQuotes

by com.satellitequotes
OverviewDiscussionsAdmin

Get the embed snippet and platform steps

get_install_snippet

The exact script tag to paste, plus ordered steps for the given platform. Pass the contractor's own token if you have it; otherwise the snippet comes back with a placeholder and instructions for finding the real one.

Input Schema

NameRequiredDescriptionDefault
modeNoinline embeds the tool in the page; modal opens it from a button; floating puts that button in the corner of every page.
tokenNoThe contractor's public token, beginning pk_live_.
serviceNoTrade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, gutter_cleaning, siding, painting, roof_cleaning, pressure_washing, house_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, lawn_treatment, leaf_removal, mosquito_control, pools, snow_removal, land_clearing, holiday_lighting. Defaults to the contractor's own default trade.
platformNoPlatform id or name, e.g. wordpress, squarespace, wix, webflow, shopify, godaddy, html, google-tag-manager. Omit for the generic snippet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"inline embeds the tool in the page; modal opens it from a button."New value: +"inline embeds the tool in the page; modal opens it from a button; floating puts that button in the corner of every page."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "inline",
-  "modal"
-]New value: +[
+  "inline",
+  "modal",
+  "floating"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Trade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, siding, painting, roof_cleaning, pressure_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, pools, snow_removal, land_clearing, holiday_lighting. Defaults to the contractor's own default trade."New value: +"Trade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, gutter_cleaning, siding, painting, roof_cleaning, pressure_washing, house_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, lawn_treatment, leaf_removal, mosquito_control, pools, snow_removal, land_clearing, holiday_lighting. Defaults to the contractor's own default trade."
  3. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Trade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, siding, painting, roof_cleaning, pressure_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, pools, snow_removal, land_clearing. Defaults to the contractor's own default trade."New value: +"Trade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, siding, painting, roof_cleaning, pressure_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, pools, snow_removal, land_clearing, holiday_lighting. Defaults to the contractor's own default trade."
  4. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Trade the widget should quote. Currently only: roofing. For other trades, use estimate_cost for a ballpark instead."New value: +"Trade the widget should quote, set as data-service on the embed tag: roofing, gutters, gutter_guards, siding, painting, roof_cleaning, pressure_washing, solar, paving, sealcoating, concrete, pavers, decks, fencing, landscaping, sod, turf, irrigation, pools, snow_removal, land_clearing. Defaults to the contractor's own default trade."
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose a genuinely useful behavioral trait — the degraded path where a missing token yields a placeholder plus instructions for finding the real one — but says nothing about auth requirements, error behavior for an unrecognized platform, or whether the operation has any side effects.

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 sentences, front-loaded with the deliverable (script tag + ordered steps) followed by the one conditional the caller must decide. No filler, no restating of the tool name.

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 and no annotations, the description does the right work: it says what is returned and how the token affects the result. Minor gaps remain around omitted-platform behavior (generic snippet) and error handling, but an agent has enough to call this correctly.

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%, so the baseline is 3, and the description earns above that by explaining the consequence of omitting token (placeholder output plus recovery instructions). It doesn't add detail on mode or service beyond the schema, but the token fallback semantics are real added meaning.

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 states specifically what comes back: 'the exact script tag to paste, plus ordered steps for the given platform.' That is a concrete resource (embed snippet + install steps) and is clearly distinct from siblings like verify_installation and list_platforms, though it never names those siblings explicitly.

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?

There is clear conditional guidance for the token parameter ('pass the contractor's own token if you have it; otherwise...'), but nothing says when to reach for this tool versus list_platforms or verify_installation, or what to do if the platform id is unknown. Usage is implied by the purpose rather than stated.

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

All SatelliteQuotes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources