Skip to main content
Glama
Sign In

Orb Studio news radars

by io.github.farenberglord-star
OverviewDiscussionsAdmin

Painter: city by the sea (radars and sensors as a picture)

get_canvas
Read-only

Orb Studio's data painter: every 3 hours the 7 news radars and the market/network sensors become a picture of a city by the sea, drawn by fixed public rules: 7 towers = 7 radars (height and lit windows = index), sky = overall tension (clear morning → storm), lightning = crypto volatility spikes, lighthouse beam = jump in Wikipedia attention, dark ships = UK sanctions list, waves = how much the radars moved. Returns the sky style, tension, tones, scene elements, the full data → picture mapping and image links (PNG and SVG); the picture itself is attached as an image block (include_image=false to skip). Data art, not weather and not a forecast. Page: https://orbstudio.org/canvas

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotNoUTC slot start, every 3 hours (default: current)
include_imageNoAttach the picture itself as a PNG image block, 480×600 (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_image
      Added value: +{
+  "description": "Attach the picture itself as a PNG image block, 480×600 (default true)",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, it discloses the three-hour cadence, deterministic public drawing rules, detailed visual encodings, structured result contents, PNG/SVG links, and default image-block attachment with an opt-out. Clarifying that the result is data art rather than a forecast further prevents misinterpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and cadence are front-loaded, followed by the encoding, outputs, image behavior, and an important caveat in a logical order. The opening sentence is long and densely packed with visual mappings, making it less scannable, although most of the detail is useful because there is no output schema.

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?

For a two-parameter read operation without an output schema, the definition supplies unusually complete invocation and interpretation context: inputs are covered by the schema, while outputs, visual semantics, cadence, attachment behavior, and external documentation are described here. An agent has enough information to select the tool, choose whether to attach the image, and understand what it receives.

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 coverage is 100%, and both slot and include_image already have clear defaults and meanings. The description repeats the cadence and image opt-out, with some useful context about links versus the attached image block, but adds no new slot-selection details such as historical availability or valid range.

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 identifies a specific transformation—turning seven news radars and market/network sensors into a city-by-the-sea data-art picture—and lists the resulting artifacts. Its visual encoding and explicit statement that this is “Data art, not weather and not a forecast” make it readily distinguishable from raw-data siblings such as get_radars and get_sensors.

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?

The description establishes a clear use case: obtaining a fixed-rule artistic representation and its underlying data-to-picture mapping, while explicitly excluding weather or forecasting interpretations. It does not directly tell agents to use get_radars, get_sensors, or another sibling when they need raw measurements rather than the artwork.

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

All Orb Studio news radars 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