Skip to main content
Glama
SynapCores MCP Server

SynapCores MCP Server

Official

SynapCores SQL reference

sql_manual
Read-onlyIdempotent

Look up SynapCores SQL syntax and examples for a topic or category before writing queries, including AI functions like EMBED and COSINE_SIMILARITY. Reads built-in docs only, never your data.

Instructions

Look up SynapCores SQL syntax and examples for one topic (for example SELECT, CREATE TABLE, EMBED, COSINE_SIMILARITY or ASK), or browse a whole category. Use it before writing SQL for query or execute, especially SynapCores-specific AI functions; it reads built-in documentation only and never touches your data. An unknown topic returns an error listing topics you can use.

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

Input Schema

NameRequiredDescriptionDefault
topicNoStatement or function to look up, for example 'SELECT', 'CREATE TABLE', 'EMBED' or 'COSINE_SIMILARITY'.
categoryNoBrowse a whole category instead of one topic: statements, functions, operators, types or all (default all).all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / category / description
      Previous value: -"Category to browse (default: all)"New value: +"Browse a whole category instead of one topic: statements, functions, operators, types or all (default all)."
    • changedInput schema / properties / topic / description
      Previous value: -"Topic to look up (e.g., 'SELECT', 'CREATE TABLE', 'EMBED', 'COSINE_SIMILARITY')"New value: +"Statement or function to look up, for example 'SELECT', 'CREATE TABLE', 'EMBED' or 'COSINE_SIMILARITY'."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond annotations: it only reads built-in documentation, never touches user data, and unknown topics return an error listing valid topics.

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 sentences, front-loaded with purpose, then usage guidance, then error behavior. Every sentence adds useful information and there is no redundant wording.

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?

The tool is a documentation lookup with two fully described optional parameters and rich annotations. The description covers purpose, usage, safety behavior, and invalid-topic handling, which is sufficient for this complexity.

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?

Schema coverage is 100%, so the baseline is 3. The description adds some value by clarifying the topic-vs-category split and by explaining what happens when an unknown topic is supplied: an error listing usable topics.

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 states a specific verb and resource: 'Look up SynapCores SQL syntax and examples' for one topic or a category. It distinguishes itself from query/execute by saying it reads built-in documentation only and never touches data.

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 says to use it before writing SQL for `query` or `execute`, especially for SynapCores-specific AI functions. It also clarifies the tool's role as documentation-only, which rules out using it for execution.

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