Skip to main content
Glama
Sign In
ArcadeDB Multi-Model DBMS

ArcadeDB Multi-Model DBMS

Official
by ArcadeData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

profiler_start

Begin recording query execution data, capturing execution times and plans for performance analysis. Configure a timeout (default 60 seconds) for automatic stopping, or end early to retrieve results.

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.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Without annotations, the description fully discloses behavior: it records all queries with execution times and plans, auto-stops after timeout, and provides instructions for manual stop and status checks.

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?

Three concise sentences: first states purpose, second details behavior, third provides usage guidance for siblings. No superfluous information.

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?

Given one optional parameter and no output schema, the description covers all necessary aspects: start, auto-stop, manual stop, and status check. It is complete for effective use.

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?

The sole parameter timeoutSeconds is fully described in the schema (including default, min, max). The description reinforces the default value but adds no new semantic meaning beyond the schema.

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 verb ('Start') and resource ('query profiler') and captures query execution data. It distinguishes itself from siblings profiler_status and profiler_stop by focusing on initiation.

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?

The description explicitly mentions when to use alternatives: 'Use profiler_stop to stop early and get results, or profiler_status to check progress.' It also explains the auto-stop behavior.

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