Skip to main content
Glama

Lantern Works GPU Prices: daily GPU rental price comparison

compare_deals

Read-only

Compare 2-5 deals side by side (price, unit, offer type, code, verification), best value first.

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": {
      "ids": "<ids>"
    },
    "name": "compare_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
modeNofull

Output Schema

NameRequiredDescriptionDefault
okYes
modeNo
dealsNo
errorNo
referral_disclosureNoOne-line referral disclosure, present whenever the result names a provider; each provider-naming item then has tracked_url (tagged /go/ redirect).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / referral_disclosure
      Added value: +{
      +  "description": "One-line referral disclosure, present whenever the result names a provider; each provider-naming item then has tracked_url (tagged /go/ redirect).",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • changedOutput schema / properties / error / properties / code / enum
      Previous value: -[
      -  "invalid_argument",
      -  "invalid_cursor",
      -  "not_found",
      -  "feed_unavailable",
      -  "feed_invalid",
      -  "upstream_unavailable",
      -  "internal_error"
      -]New value: +[
      +  "invalid_argument",
      +  "invalid_cursor",
      +  "cursor_expired",
      +  "not_found",
      +  "feed_unavailable",
      +  "feed_invalid",
      +  "upstream_unavailable",
      +  "internal_error"
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful traits beyond them: an input cardinality limit of 2-5, the set of attributes compared, and a ranked output with best value first. It does not cover what happens outside the 2-5 range or what 'full' mode changes, but with annotations and an output schema present the bar is lower.

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?

A single front-loaded sentence that packs the operation, the limits, the compared fields, and the sort order with no redundant or filler wording.

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

Completeness3/5

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

The output schema and annotations relieve the description of explaining return values and safety, and the comparison semantics are clear. However, for a two-parameter tool, the total silence on 'mode' and the unspecified 'ids' encoding are real gaps an agent must guess at before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description only indirectly touches the parameters: '2-5 deals' hints at how many identifiers go in 'ids', but never states the format (comma-separated string? repeated key?). The 'mode' parameter, which defaults to 'full', is not mentioned at all, leaving an undocumented behavior switch.

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 (compare deals), a cardinality bound (2-5), the exact comparison dimensions (price, unit, offer type, code, verification), and the output ordering (best value first). This is enough to distinguish it from get_deal (single deal) and search_deals (discovery) without opening any schema.

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?

The '2-5 deals' bound implies when the tool is applicable, but there is no explicit when-to-use/when-not guidance and no named alternative for the single-deal case (get_deal) or for finding deals in the first place (search_deals). Usage is inferable 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.