Speak To Your Database (STYD)

List connections

list_connections

Read-onlyIdempotent

Use this when the user asks what is connected or how to connect data, or when you need a connection_id because the user has several data sources. Not needed before asking: with one data source, ask_question uses it. Lists the user's Odoo, PostgreSQL and MySQL connections with their connection_id, workspace and an access state:

ready: questions can be asked.
not_mapped (Odoo Bridge only): a workspace owner or admin must link the user's STYD account to an Odoo user first. Odoo API-key connections need no linking.
not_ready: the connection's setup is not finished. When nothing of the user's own is connected, the result says how to connect it. Uses no prompt.

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

Input Schema

Name	Required	Description	Default
`workspace_id`	No	Optional. Only list this workspace's connections (a workspace_id from list_workspaces or an earlier result).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / workspace_id / description

Added value: +"Optional. Only list this workspace's connections (a workspace_id from list_workspaces or an earlier result)."

First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: the three access states and their meanings, which state requires an admin action, the Odoo API-key exception, the fallback when nothing is connected, and that it consumes no prompt. This is behavioral detail not derivable from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, then a scannable bullet list of states, with no filler sentences. Phrasing such as 'Not needed before asking: with one data source, ask_question uses it' is slightly compressed and stumbles on first read.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the meaning of each access state. For a one-optional-param read tool it leaves nothing an agent needs before calling it.

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% and the single optional workspace_id parameter is fully documented in the schema, so the baseline is 3. However, the description never mentions the workspace filter or how it interacts with the returned 'workspace' field, so it adds no 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?

States a specific verb and resource ('Lists the user's Odoo, PostgreSQL and MySQL connections') and names the exact fields returned (connection_id, workspace, access state). It is clearly separable from siblings like list_workspaces and ask_question.

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?

Explicitly states when to call ('user asks what is connected', 'you need a connection_id because the user has several data sources') and when not to ('Not needed before asking: with one data source, ask_question uses it'). It also routes behavior per access state, naming the remediation for not_mapped.

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

All Speak To Your Database (STYD) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.