TranscriptFetch

Check a monitor now

check_monitor_now

Run a monitor's check now instead of waiting for its schedule, and return the new videos it found. Costs 1 credit, like a scheduled check (free when the listing fails), plus transcripts for a monitor that delivers them. The next scheduled check counts from now. Takes up to about a minute and a half.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "check_monitor_now"
  }
}

Input Schema

Name	Required	Description	Default
`monitor_id`	Yes	The monitor's id (mon_…), from list_monitors or create_monitor.
`timestamps`	No	Include each transcript's timestamped segments (default false).

Output Schema

Name	Required	Description
`error`	No	Present when the check ran but its listing failed; nothing was charged.
`videos`	No	The videos found, newest event first.
`balance`	No	Remaining credit balance after this call, when known.
`monitor`	No	A monitor. The webhook signing secret is never shown here.
`newVideos`	No	New videos this check found.
`creditsSpent`	No	Credits charged for this call (0 on failure or for admins).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds substantial context beyond annotations: credit cost, free checks when listing fails, transcript charges, resetting the next scheduled check, and duration of up to about a minute and a half. These are meaningful side effects and operational constraints for a non-idempotent, open-world tool. This is exactly the kind of behavioral detail annotations alone cannot convey.

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?

The description is a compact paragraph that front-loads the main action, then adds cost, scheduling side effect, and duration. Every sentence contributes useful operational context without repetition. It is appropriately sized for a tool with this many behavioral caveats.

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?

The description covers the key behavioral traits an agent needs: manual trigger, returned videos, credit cost, failure cost, transcript charges, schedule reset, and latency. An output schema exists, so return value detail is not required in the description. Nothing important for correct invocation is missing.

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 description coverage is 100%, so the schema already documents monitor_id and timestamps adequately. The description does not add syntax or format details for either parameter beyond the schema. Baseline 3 is appropriate because the schema carries the parameter semantics.

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 opens with a specific verb and resource: run a monitor's check now instead of waiting for its schedule. It also states that the tool returns newly found videos, which distinguishes it from passive listing tools like get_new_videos. An agent can understand exactly what action this tool performs without opening the 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?

The description clearly establishes when to use it: when you want a check now rather than waiting for the scheduled run. It does not name explicit alternatives or exclusions, but the triggering context is unambiguous. The only missing piece is guidance on when not to use it or which sibling to choose for related read-only operations.

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

All TranscriptFetch tools Inspect

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.