Skip to main content
Glama

Deadline events: interview forecasts that just came true or failed

get_interview_events
Read-only

Impulse feed: every day Orb Studio re-checks interview price targets whose deadline has passed against Kraken prices and posts an event (target reached / not reached), plus a scoreboard of speakers (how many of their checked price targets came true, failed or are pending). Use it before you repeat a famous forecast.

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_interview_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a daily re-check cadence, the external price source (Kraken), and the two things returned (events and a speaker scoreboard). It stays silent on pagination or how days/limit bound the result set.

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?

Front-loaded with the "Impulse feed" framing, then a single dense sentence, then the usage cue. Multi-clause parentheticals make it slightly rambling, but every clause conveys real information about output content or provenance.

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?

With no output schema, the description does the necessary work of sketching the return payload (events with reached/not-reached outcomes plus a per-speaker scoreboard). However, with two undocumented parameters and no statement of result volume or ordering, it is not complete enough for confident invocation.

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?

Both parameters (days, limit) have 0% schema description coverage, so the description carries the full burden of explaining them — and it never mentions either one. An agent cannot tell from the text whether days bounds the lookback window or the deadline window, nor what limit caps.

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?

The description states a concrete resource and scope: deadline-passed interview price targets re-checked against Kraken prices, emitting reached/not-reached events plus a speaker scoreboard. That is far more specific than the name alone and implies a different output than sibling checks tools, though it never explicitly contrasts itself with get_interview_checks or check_interview.

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?

It gives one explicit when-to-use trigger: "Use it before you repeat a famous forecast." That is real guidance but narrow and informal, with no when-not conditions and no named alternative for checking a live or pending target (the obvious sibling use case).

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.