<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on MCP Toolbox for Databases</title><link>/integrations/spanner/tools/</link><description>Recent content in Tools on MCP Toolbox for Databases</description><generator>Hugo</generator><language>en</language><atom:link href="/integrations/spanner/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>spanner-execute-sql</title><link>/integrations/spanner/tools/spanner-execute-sql/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/integrations/spanner/tools/spanner-execute-sql/</guid><description>&lt;h2 id="about">About&lt;/h2>
&lt;p>A &lt;code>spanner-execute-sql&lt;/code> tool executes a SQL statement against a Spanner
database.&lt;/p>
&lt;p>&lt;code>spanner-execute-sql&lt;/code> takes one input parameter &lt;code>sql&lt;/code> and run the sql
statement against the &lt;code>source&lt;/code>.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> This tool is intended for developer assistant workflows with
human-in-the-loop and shouldn&amp;rsquo;t be used for production agents.&lt;/p>&lt;/blockquote>
&lt;h2 id="compatible-sources">Compatible Sources&lt;/h2>



&lt;div class="compatibility-section">
 &lt;p>This tool can be used with the following database sources:&lt;/p>

 &lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Source Name&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 
 
 &lt;tr>
 &lt;td>&lt;a href="/integrations/spanner/">Spanner&lt;/a>&lt;/td>
 &lt;/tr>
 

 
 
 
 &lt;/tbody>
 &lt;/table>
&lt;/div>
&lt;h2 id="example">Example&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-yaml" data-lang="yaml">&lt;span class="line">&lt;span class="cl">&lt;span class="nt">kind&lt;/span>&lt;span class="p">:&lt;/span>&lt;span class="w"> &lt;/span>&lt;span class="l">tool&lt;/span>&lt;span class="w">
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="w">&lt;/span>&lt;span class="nt">name&lt;/span>&lt;span class="p">:&lt;/span>&lt;span class="w"> &lt;/span>&lt;span class="l">execute_sql_tool&lt;/span>&lt;span class="w">
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="w">&lt;/span>&lt;span class="nt">type&lt;/span>&lt;span class="p">:&lt;/span>&lt;span class="w"> &lt;/span>&lt;span class="l">spanner-execute-sql&lt;/span>&lt;span class="w">
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="w">&lt;/span>&lt;span class="nt">source&lt;/span>&lt;span class="p">:&lt;/span>&lt;span class="w"> &lt;/span>&lt;span class="l">my-spanner-instance&lt;/span>&lt;span class="w">
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="w">&lt;/span>&lt;span class="nt">description&lt;/span>&lt;span class="p">:&lt;/span>&lt;span class="w"> &lt;/span>&lt;span class="l">Use this tool to execute sql statement.&lt;/span>&lt;span class="w">
&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="reference">Reference&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>&lt;strong>field&lt;/strong>&lt;/th>
 &lt;th style="text-align: center">&lt;strong>type&lt;/strong>&lt;/th>
 &lt;th style="text-align: center">&lt;strong>required&lt;/strong>&lt;/th>
 &lt;th>&lt;strong>description&lt;/strong>&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>type&lt;/td>
 &lt;td style="text-align: center">string&lt;/td>
 &lt;td style="text-align: center">true&lt;/td>
 &lt;td>Must be &amp;ldquo;spanner-execute-sql&amp;rdquo;.&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>source&lt;/td>
 &lt;td style="text-align: center">string&lt;/td>
 &lt;td style="text-align: center">true&lt;/td>
 &lt;td>Name of the source the SQL should execute on.&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>description&lt;/td>
 &lt;td style="text-align: center">string&lt;/td>
 &lt;td style="text-align: center">true&lt;/td>
 &lt;td>Description of the tool that is passed to the LLM.&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>readOnly&lt;/td>
 &lt;td style="text-align: center">bool&lt;/td>
 &lt;td style="text-align: center">false&lt;/td>
 &lt;td>When set to &lt;code>true&lt;/code>, the &lt;code>statement&lt;/code> is run as a read-only transaction. Default: &lt;code>false&lt;/code>.&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table></description></item><item><title>spanner-sql</title><link>/integrations/spanner/tools/spanner-sql/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/integrations/spanner/tools/spanner-sql/</guid><description>&lt;h2 id="about">About&lt;/h2>
&lt;p>A &lt;code>spanner-sql&lt;/code> tool executes a pre-defined SQL statement (either &lt;code>googlesql&lt;/code> or
&lt;code>postgresql&lt;/code>) against a Cloud Spanner database.&lt;/p>
&lt;h2 id="compatible-sources">Compatible Sources&lt;/h2>



&lt;div class="compatibility-section">
 &lt;p>This tool can be used with the following database sources:&lt;/p>

 &lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Source Name&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 
 
 &lt;tr>
 &lt;td>&lt;a href="/integrations/spanner/">Spanner&lt;/a>&lt;/td>
 &lt;/tr>
 

 
 
 
 &lt;/tbody>
 &lt;/table>
&lt;/div>
&lt;h3 id="googlesql">GoogleSQL&lt;/h3>
&lt;p>For the &lt;code>googlesql&lt;/code> dialect, the specified SQL statement is executed as a &lt;a href="https://cloud.google.com/spanner/docs/reference/standard-sql/dml-syntax">data
manipulation language (DML)&lt;/a> statements, and specified parameters will
inserted according to their name: e.g. &lt;code>@name&lt;/code>.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> This tool uses parameterized queries to prevent SQL injections.
Query parameters can be used as substitutes for arbitrary expressions.
Parameters cannot be used as substitutes for identifiers, column names, table
names, or other parts of the query.&lt;/p></description></item><item><title>spanner-list-graphs</title><link>/integrations/spanner/tools/spanner-list-graphs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/integrations/spanner/tools/spanner-list-graphs/</guid><description>&lt;h2 id="about">About&lt;/h2>
&lt;p>A &lt;code>spanner-list-graphs&lt;/code> tool retrieves comprehensive schema information about
graphs in a Cloud Spanner database. It returns detailed metadata including
node tables, edge tables, labels and property declarations.&lt;/p>
&lt;h3 id="features">Features&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Comprehensive Schema Information&lt;/strong>: Returns node tables, edge tables, labels
and property declarations&lt;/li>
&lt;li>&lt;strong>Flexible Filtering&lt;/strong>: Can list all graphs or filter by specific graph names&lt;/li>
&lt;li>&lt;strong>Output Format Options&lt;/strong>: Choose between simple (graph names only) or detailed
(full schema information) output&lt;/li>
&lt;/ul>
&lt;h3 id="use-cases">Use Cases&lt;/h3>
&lt;ol>
&lt;li>&lt;strong>Database Documentation&lt;/strong>: Generate comprehensive documentation of your
database schema&lt;/li>
&lt;li>&lt;strong>Schema Validation&lt;/strong>: Verify that expected graphs, node and edge exist&lt;/li>
&lt;li>&lt;strong>Migration Planning&lt;/strong>: Understand the current schema before making changes&lt;/li>
&lt;li>&lt;strong>Development Tools&lt;/strong>: Build tools that need to understand database structure&lt;/li>
&lt;li>&lt;strong>Audit and Compliance&lt;/strong>: Track schema changes and ensure compliance with
data governance policies&lt;/li>
&lt;/ol>
&lt;p>This tool is read-only and executes pre-defined SQL queries against the
&lt;code>INFORMATION_SCHEMA&lt;/code> tables to gather metadata.
&lt;style type="text/css">
 
 .notice {
 --title-color: #fff;
 --title-background-color: #6be;
 --content-color: #444;
 --content-background-color: #e7f2fa;
 }

 .notice.info {
 --title-background-color: #fb7;
 --content-background-color: #fec;
 }

 .notice.tip {
 --title-background-color: #5a5;
 --content-background-color: #efe;
 }

 .notice.warning {
 --title-background-color: #c33;
 --content-background-color: #fee;
 }

 
 @media (prefers-color-scheme:dark) {
 .notice {
 --title-color: #fff;
 --title-background-color: #069;
 --content-color: #ddd;
 --content-background-color: #023;
 }

 .notice.info {
 --title-background-color: #a50;
 --content-background-color: #420;
 }

 .notice.tip {
 --title-background-color: #363;
 --content-background-color: #121;
 }

 .notice.warning {
 --title-background-color: #800;
 --content-background-color: #400;
 }
 }

 body.dark .notice {
 --title-color: #fff;
 --title-background-color: #069;
 --content-color: #ddd;
 --content-background-color: #023;
 }

 body.dark .notice.info {
 --title-background-color: #a50;
 --content-background-color: #420;
 }

 body.dark .notice.tip {
 --title-background-color: #363;
 --content-background-color: #121;
 }

 body.dark .notice.warning {
 --title-background-color: #800;
 --content-background-color: #400;
 }

 
 .notice {
 padding: 18px;
 line-height: 24px;
 margin-bottom: 24px;
 border-radius: 4px;
 color: var(--content-color);
 background: var(--content-background-color);
 }

 .notice p:last-child {
 margin-bottom: 0
 }

 
 .notice-title {
 margin: -18px -18px 12px;
 padding: 4px 18px;
 border-radius: 4px 4px 0 0;
 font-weight: 700;
 color: var(--title-color);
 background: var(--title-background-color);
 }

 
 .icon-notice {
 display: inline-flex;
 align-self: center;
 margin-right: 8px;
 }

 .icon-notice img,
 .icon-notice svg {
 height: 1em;
 width: 1em;
 fill: currentColor;
 }

 .icon-notice img,
 .icon-notice.baseline svg {
 top: .125em;
 position: relative;
 }
&lt;/style>&lt;div class="notice warning" >
 &lt;p class="notice-title">
 &lt;span class="icon-notice baseline">
 &lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="126 76.5 300 300">
 &lt;path d="M297.431 324.397v-34.255c0-3.245-2.344-5.95-5.358-5.95h-32.146c-3.014 0-5.358 2.705-5.358 5.95v34.255c0 3.245 2.344 5.95 5.358 5.95h32.146c3.014 0 5.358-2.705 5.358-5.95Zm-.335-67.428 3.014-82.753c0-1.081-.502-2.524-1.674-3.425-1.005-.902-2.512-1.983-4.019-1.983h-36.834c-1.507 0-3.014 1.081-4.019 1.983-1.172.901-1.674 2.704-1.674 3.786l2.846 82.392c0 2.344 2.512 4.146 5.693 4.146h30.975c3.013 0 5.525-1.803 5.692-4.146Zm-2.344-168.39L423.34 342.425c3.683 7.032 3.516 15.686-.335 22.717-3.85 7.031-10.883 11.358-18.417 11.358H147.413c-7.534 0-14.566-4.327-18.417-11.358-3.85-7.031-4.018-15.685-.335-22.716L257.248 88.578C260.93 81.188 268.13 76.5 276 76.5c7.87 0 15.069 4.688 18.752 12.08Z"/>
&lt;/svg>

 &lt;/span>Warning&lt;/p></description></item><item><title>spanner-list-tables</title><link>/integrations/spanner/tools/spanner-list-tables/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/integrations/spanner/tools/spanner-list-tables/</guid><description>&lt;h2 id="about">About&lt;/h2>
&lt;p>A &lt;code>spanner-list-tables&lt;/code> tool retrieves comprehensive schema information about
tables in a Cloud Spanner database. It automatically adapts to the database
dialect (GoogleSQL or PostgreSQL) and returns detailed metadata including
columns, constraints, and indexes.&lt;/p>
&lt;p>This tool is read-only and executes pre-defined SQL queries against the
&lt;code>INFORMATION_SCHEMA&lt;/code> tables to gather metadata. The tool automatically detects
the database dialect from the source configuration and uses the appropriate SQL
syntax.&lt;/p>
&lt;h3 id="features">Features&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Automatic Dialect Detection&lt;/strong>: Adapts queries based on whether the database
uses GoogleSQL or PostgreSQL dialect&lt;/li>
&lt;li>&lt;strong>Comprehensive Schema Information&lt;/strong>: Returns columns, data types, constraints,
indexes, and table relationships&lt;/li>
&lt;li>&lt;strong>Flexible Filtering&lt;/strong>: Can list all tables or filter by specific table names&lt;/li>
&lt;li>&lt;strong>Output Format Options&lt;/strong>: Choose between simple (table names only) or detailed
(full schema information) output&lt;/li>
&lt;/ul>
&lt;h3 id="use-cases">Use Cases&lt;/h3>
&lt;ol>
&lt;li>&lt;strong>Database Documentation&lt;/strong>: Generate comprehensive documentation of your
database schema&lt;/li>
&lt;li>&lt;strong>Schema Validation&lt;/strong>: Verify that expected tables and columns exist&lt;/li>
&lt;li>&lt;strong>Migration Planning&lt;/strong>: Understand the current schema before making changes&lt;/li>
&lt;li>&lt;strong>Development Tools&lt;/strong>: Build tools that need to understand database structure&lt;/li>
&lt;li>&lt;strong>Audit and Compliance&lt;/strong>: Track schema changes and ensure compliance with
data governance policies&lt;/li>
&lt;/ol>
&lt;h2 id="compatible-sources">Compatible Sources&lt;/h2>



&lt;div class="compatibility-section">
 &lt;p>This tool can be used with the following database sources:&lt;/p></description></item></channel></rss>