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

Assetto Corsa Cinematic Director MCP

by Metalroachtwo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restore_original_configuration

Reverts Assetto Corsa settings to their original state when needed; in v0.2.0 this is a no-op because the server never changes game configuration.

Instructions

No-op: v0.2.0 never changes game configuration.

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": "restore_original_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool is a no-op and never changes configuration, which covers the core behavior. However, it omits details like return value (likely nothing) or side effects (none), though these are trivial for a no-op.

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 single, front-loaded sentence with no unnecessary words. It efficiently conveys the key fact that the tool does nothing.

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 zero-parameter no-op tool, the description provides enough context to understand its behavior. It does not explain why the tool exists (e.g., backward compatibility) or whether it will be removed, but the essential information is present.

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?

The tool has zero parameters, so the schema coverage is trivially 100% and the baseline score is 4. The description adds no parameter information, which is appropriate since there are none.

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 the tool is a no-op and clarifies that it never changes game configuration, which directly contradicts the name's implication. It provides a specific fact about the tool's behavior, making the purpose clear despite the misleading name.

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?

The description does not explicitly state when to use or avoid this tool. It implies that calling it has no effect, but there is no directive such as 'do not call' or 'use X instead', leaving the agent to infer that it should be skipped.

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