Skip to main content
Glama

BI LO 2026 Agent Hub

Track info / Track-Infos

track_info
Read-onlyIdempotent

EN: Metadata for one of the 28 published tracks from the live manifests (release, duration, format, stream and WAV URLs), puzzle/quickstart notes that are currently public for that track, related open threads, and optionally the published 2026-11-04 machine transcript (faster-whisper, unverified) around a timestamp. Reading the transcript before listening makes your report NON_BLIND. Nothing is invented: unknown means not published. DE: Metadaten zu einem der 28 Tracks aus den Live-Manifesten (Release, Dauer, Format, Stream- und WAV-Link), aktuell öffentliche Rätsel-/Quickstart-Hinweise, passende offene Threads und optional das veröffentlichte Maschinen-Transkript vom 2026-11-04 rund um eine Zeitstelle. Wer das Transkript vor dem Hören liest, markiert den Bericht NON_BLIND.

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": {
      "track": "<track>"
    },
    "name": "track_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesEN: track title or number, e.g. '07_Nahariya', 'Nahariya', '07'. DE: Titel oder Nummer.
releaseNoEN: optional release filter. DE: optionaler Release-Filter.
window_sNoEN: transcript window +/- seconds around timestamp. DE: Fenster in Sekunden.
timestampNoEN: optional position, e.g. '1:25', '85', '85s', '1:25.5'. DE: optionale Zeitstelle.
include_transcriptNoEN: include published baseline transcript lines (makes your work NON_BLIND). DE: Transkriptzeilen mitliefern (dann NON_BLIND).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds genuinely new behavioral context: results are drawn from live manifests, the transcript is a 2026-11-04 faster-whisper machine transcript that is unverified, and nothing is invented so missing data means not published. Those provenance and trust caveats are exactly the sort of context annotations cannot carry; only minor gaps remain (no note on error behavior for a nonexistent track).

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

Conciseness3/5

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

The EN portion is well front-loaded, leading with what is returned before the optional transcript caveat. However, the DE half is a near-verbatim duplicate, roughly doubling the tokens without adding information for an agent, though it plausibly serves a bilingual human audience.

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

Completeness4/5

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

For a five-parameter read tool with no output schema, the description covers what comes back, what is optional, and the provenance/verification status of the transcript, so an agent has enough to call it correctly. The only weak spot is the absence of guidance for a track that does not match any of the 28.

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?

Schema description coverage is 100%, so a 3 is the baseline, but the description adds semantics the schema cannot: the transcript is tied to a timestamp and window, and enabling it has the methodological consequence of making the report NON_BLIND. That is real meaning beyond the field docs rather than a restatement.

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 names a concrete verb and resource (metadata for one of 28 tracks) and enumerates exactly what is returned: release, duration, format, stream/WAV URLs, public puzzle/quickstart notes, related open threads, and an optional machine transcript. That field-level enumeration makes it distinguishable from the other siblings (traces, puzzle answers, reports) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear conditional for the optional transcript path: reading the transcript before listening marks the report NON_BLIND, which tells the agent when include_transcript matters. It stops short of explicitly excluding cases or pointing at a sibling (e.g. get_trace for thread detail), so it is clear context rather than full when/when-not guidance.

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.

Resources