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

ArcadeDB Multi-Model DBMS

Official
by ArcadeData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

query

Execute read-only, idempotent queries on an ArcadeDB database using Cypher, SQL, Gremlin, GraphQL, or MongoDB. Supports SELECT, MATCH, and other read operations.

Instructions

Execute a read-only (idempotent) query against an ArcadeDB database. Use this for SELECT, MATCH, and other read operations. Prefer OpenCypher (language: 'cypher') unless SQL is explicitly requested.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database": "<database>",
      "query": "<query>"
    },
    "name": "query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 1000)
queryYesThe query to execute
databaseYesThe name of the database to query
languageNoQuery language: 'sql', 'cypher', 'gremlin', 'graphql', 'mongo'cypher

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The description states read-only and idempotent behavior, which are key traits. However, with no annotations, more details about error handling or limitations would improve transparency.

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?

Two sentences, no fluff, front-loaded with purpose. Every part is valuable and efficiently conveyed.

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

Completeness3/5

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

Adequate for a query tool with 4 parameters and no output schema. Could be improved by mentioning return format or common usage patterns, but is sufficient.

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 coverage is 100%, so baseline is 3. The description adds context about query purpose and language preference, but does not significantly enhance parameter understanding 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 tool executes read-only queries on ArcadeDB, specifying the verb and resource. It distinguishes itself from sibling tools like execute_command by focusing on read operations.

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

Usage Guidelines4/5

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

Explicitly instructs to use for SELECT, MATCH, and other read operations, and recommends preferring OpenCypher unless SQL is requested. This provides clear context for when to use this tool, though it does not explicitly mention exclusions.

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