Skip to main content
Glama
Sign In
Assetto Corsa Cinematic Director MCP

Assetto Corsa Cinematic Director MCP

by Metalroachtwo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_live_replay_status

Read a fresh, bounded replay status snapshot to monitor Assetto Corsa replay state without sending commands to CSP.

Instructions

Read a fresh, bounded status snapshot; never sends commands to CSP.

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

Input Schema

NameRequiredDescriptionDefault
game_dirNo
max_age_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute real signal: the operation is read-only and will not issue commands to CSP. However, it omits what happens when the data is stale (does it error, block, or return a flag), what CSP is, and whether the read refreshes anything.

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?

A single tight sentence with the read-only guarantee front-loaded and no filler. It is efficient, though its brevity edges toward under-specification rather than pure conciseness.

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

Completeness2/5

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

No annotations, no output schema, and two fully undocumented parameters mean the description must do the heavy lifting, and it does not. An agent still cannot tell what fields the snapshot returns or how the selector parameters behave.

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?

Schema description coverage is 0%, so neither game_dir nor max_age_seconds is documented anywhere. The description's 'fresh, bounded' hints at the max_age_seconds default of 5 but never names or explains it, and game_dir is not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It gives a verb plus a resource ('Read a fresh, bounded status snapshot'), but the resource is never identified as live-replay status, and 'CSP' is unexplained jargon. An agent can infer it is a read-only status probe, yet not what the snapshot actually reports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no reference to any sibling such as probe_replay_bridge or list_saved_replays, which are the closest alternatives. The contrast is only implicit in 'never sends commands'.

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

Deploy Server

Other Tools