Skip to main content
Glama
ArcadeData

ArcadeDB Multi-Model DBMS

Official

profiler_start

Start capturing query execution data including execution times and plans in ArcadeDB. The profiler automatically stops after a configurable timeout or can be stopped manually to analyze performance.

Instructions

Start the query profiler to capture query execution data. The profiler records all queries with their execution times and plans. It auto-stops after the specified timeout (default 60 seconds). Use profiler_stop to stop early and get results, or profiler_status to check progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutSecondsNoRecording timeout in seconds. The profiler auto-stops after this duration. Default: 60.

Implementation Reference

  • The profilerStart function implementation sends a "profiler start [timeout]" command to the server via an AJAX POST request.
    function profilerStart() {
      var timeout = jQuery("#profilerTimeout").val() || "60";
      jQuery.ajax({
        type: "POST",
        url: "api/v1/server",
        data: JSON.stringify({ command: "profiler start " + timeout }),
        headers: { Authorization: globalCredentials },
        contentType: "application/json",
        success: function() {
          profilerStartTime = Date.now();
          profilerTimeoutMs = parseInt(timeout) * 1000;
          profilerSetRecordingUI(true);
          globalNotify("Profiler", "Recording started (auto-stop in " + timeout + "s)", "success");
        },
        error: function(jqXHR) { globalNotifyError(jqXHR.responseText); }
      });
    }
Behavior4/5

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

With no annotations, the description carries full burden and discloses key behaviors: it records queries with execution times and plans, auto-stops after a timeout (default 60 seconds), and requires profiler_stop to stop early. It lacks details on permissions or rate limits, but covers essential operational traits.

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 front-loaded with the core purpose, followed by supporting details in three efficient sentences. Each sentence adds necessary context without redundancy, making it appropriately sized and well-structured.

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?

Given the tool's moderate complexity (a start operation with one optional parameter) and no annotations or output schema, the description is largely complete. It explains what the tool does, when to use it, and key behaviors, though it could mention potential side effects or error conditions for full coverage.

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 the timeoutSeconds parameter fully. The description adds minimal value by mentioning the default timeout, but does not provide additional syntax or format details beyond what the schema specifies.

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 clearly states the specific action ('Start the query profiler') and resource ('to capture query execution data'), distinguishing it from siblings like profiler_stop and profiler_status. It specifies what the tool initiates and the scope of data recorded.

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

Usage Guidelines5/5

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

It explicitly provides when to use this tool (to start profiling) and when to use alternatives (profiler_stop to stop early, profiler_status to check progress). The guidance is direct and includes sibling tool names for context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArcadeData/arcade-db-multi-model-dbms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server