End active CSV profiling capture in Unreal Engine and save the collected data to a file.
Stop CSV profiling capture and save results.
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": "stop_csv_profiling"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It mentions 'stop capture and save results,' indicating mutation, but doesn't specify if any state changes are persistent, if it requires an active profiling session, or what the output format is. The behavior is under-disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with a clear verb and object. It is appropriately concise, though it could add a little more context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no annotations and no output schema, the description is minimal. For a state-changing tool like stopping profiling, it lacks context about the workflow (e.g., that it complements start_csv_profiling) and any effects on the system. It is not complete for an effective selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is empty with 100% coverage, so the description doesn't need to explain parameters. The description correctly implies no parameters are needed, and the baseline for no params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool stops CSV profiling and saves results, with a specific verb and resource. However, it lacks differentiation from its sibling 'start_csv_profiling' and other profiling tools, so it's not fully distinguished.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not mention when to use this tool or any context about prerequisites (e.g., it must be called after start_csv_profiling). There is no guidance on alternatives, as it's the only stop profiling tool, but usage context is minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.