Skip to main content
Glama

Lantern Works GPU Prices: daily GPU rental price comparison

get_deal

Read-only

Get one deal's public record by id, including redeem_url and agent_instructions.

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": {
      "id": "<id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
modeNofull

Output Schema

NameRequiredDescriptionDefault
okYes
modeNo
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

B3.3/5.0
Behavior3/5

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

The annotations already declare this a read-only, open-world operation, so the safety bar is low. The description adds that the record is 'public' and enumerates two fields it includes, but it never explains what the 'mode' parameter changes or what a non-default mode does, which is the main behavioral unknown.

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 with no filler; the resource and its scope come first and the notable returned fields follow.

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?

An output schema exists, so return values need not be spelled out, and the annotations cover the safety profile. Still, the undefined 'mode' parameter and the absence of any routing guidance against search/compare siblings leave real gaps for a two-parameter lookup tool.

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 description coverage is 0%, so the description must carry parameter meaning. It only gestures at 'id' ('by id') and says nothing about 'mode' despite it defaulting to 'full', which strongly implies other modes exist and their effect is left entirely undocumented.

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 ('Get one deal's public record') with a clear singular-by-id scope, which inherently separates it from list/compare siblings like search_deals and compare_deals. But it never names those alternatives, so differentiation is inferred rather than stated.

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 'by id' phrasing implies you should call this when you already have a deal identifier and want a single record, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling tool for other retrieval patterns.

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.