Skip to main content
Glama
Sign In

GlobalHostia

by com.globalhostia
OverviewDiscussionsAdmin

Compare plans side by side

compare_plans
Read-onlyIdempotent

Side-by-side comparison of 2 to 5 plans by slug: specs, price for every billing cycle (with setup fee and monthly equivalent), location and top features. Use after search_products or recommend_plan when the user is choosing between options.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYesProduct slugs to compare.
currencyNoISO 4217 currency code, e.g. USD or AED. Defaults to USD. An unsupported code returns an error listing the valid ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the 2-to-5 bound and what the comparison returns, including setup fee and monthly equivalent normalization across billing cycles, which is detail the annotations cannot convey.

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, no filler, with the capability stated first and the routing guidance second. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating what the comparison returns, so an agent knows the response shape before calling. Combined with the rich input schema and read-only annotations, nothing material is missing for a two-parameter read tool.

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 both slugs and currency are already documented, including the ISO 4217 pattern, the USD default and the unsupported-code error behavior. The description only restates the 2-to-5 cardinality that minItems/maxItems already express, adding no new semantics.

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?

States a specific verb and resource ('side-by-side comparison of 2 to 5 plans by slug') plus the exact contents compared (specs, price per billing cycle with setup fee and monthly equivalent, location, top features). An agent can distinguish this from recommend_plan or search_products without opening the schema.

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?

Explicitly says to use it after search_products or recommend_plan when the user is choosing between options, which names the preceding tools and the selecting condition. It does not state any when-not case (e.g. comparing a single plan or comparing across categories), so it falls just short of fully explicit routing.

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

All GlobalHostia 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