Skip to main content
Glama
keithrawlingsbrown

refinex-mcp

by keithrawlingsbrown
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_live_signal

Retrieve the highest-confidence active AWS spot arbitrage signal with action, region, pricing, and confidence. No API key required. If no signal, returns use_on_demand with rationale.

Instructions

Get the single best active AWS spot arbitrage signal right now. No API key required.

Returns the highest-confidence active signal including:

  • action: "buy_spot" | "migrate_spot" | "wait" | "use_on_demand"

  • cloud, region, availability_zone, instance_type

  • spot_price_usd, on_demand_price_usd, discount_pct

  • confidence (0.0–1.0, deterministic — no LLM scoring)

  • ttl_minutes: how long this signal is valid

  • suppressed_last_6h: signals detected but held back in last 6 hours

  • signal_id: use this to reference a specific signal

If no signal clears the confidence threshold, returns action="use_on_demand" with a rationale. suppressed_last_6h will still be populated.

This is the fastest way to get real AWS spot data — zero credentials needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Disclosures include: confidence is deterministic (no LLM scoring), TTL, suppression history, fallback behavior. No annotations provided, so description carries full burden; it is thorough.

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?

Well-structured: purpose first, key features, detailed return fields, fallback. No fluff, every sentence adds value.

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?

No output schema exists, but description comprehensively explains return fields and behavior. No missing context given zero parameters.

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?

No parameters exist; schema coverage is 100%. Baseline is 4 as description adds no parameter info (unnecessary).

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?

The description clearly states the verb 'Get', the resource 'active AWS spot arbitrage signal', and the scope 'single best active'. It distinguishes from siblings like get_signal_for_instance and list_signals.

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?

It explicitly notes 'No API key required' and 'fastest way', indicating when to use. However, it does not explicitly state when not to use or contrast with alternatives beyond speed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/keithrawlingsbrown/refinex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server