Skip to main content
Glama

Get context

get_context
Read-only

Get what the team wants AI tools to know about one connection: notes for AI (for example which table to prefer or what unit amounts are in), business definitions such as "active customer" with their SQL, and the description and synonyms of each described table and column. Call it once at the start of a conversation about a connection, after list_connections and before writing SQL, and follow the notes. Pass intent to get only the tables and definitions relevant to the question, which keeps the answer short on large databases. Descriptions written in SaturnSQL take the place of the database's own comments. Read-only. Refused on an approved_queries connection.

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": {
      "connectionId": "<connectionId>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNoThe user's question or goal in a few words, e.g. "revenue by customer last month". Omit for everything that has context.
connectionIdYesConnection id from list_connections.

Output Schema

NameRequiredDescriptionDefault
engineNo
tablesNo
definitionsNo
descriptionNo
connectionIdNo
instructionsNoNotes for AI from the team. Follow them.
omittedTablesNoDescribed tables left out because they did not match intent.
connectionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses two non-obvious behaviors: the call is refused on an approved_queries connection, and SaturnSQL descriptions override the database's own comments. The refusal condition is a concrete failure mode an agent cannot learn from any structured field, and the precedence rule changes how the returned text should be interpreted.

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 what the tool returns, then ordering, then parameter advice, then caveats — a sensible structure with no filler sentences. The standalone 'Read-only.' sentence duplicates the readOnlyHint annotation and is the only line that does not earn its place.

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?

An output schema exists, so return values need no explanation, and both parameters are covered by the schema plus the intent rationale. With sequencing, refusal behavior, and precedence rules all stated, an agent has everything needed to call this correctly on the first attempt.

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 would be 3; the description earns above that by explaining the purpose of intent beyond the schema's wording, namely that scoping by question keeps the response short on large databases. It adds rationale rather than new syntax, so it stops short of 5.

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?

Names a specific verb (get) and enumerates the exact resource contents: AI notes, business definitions with SQL, and table/column descriptions and synonyms. An agent can tell this apart from get_schema or list_connections because the description says the payload is curated human-authored context, not raw DDL.

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?

Gives explicit sequencing ('once at the start of a conversation about a connection, after list_connections and before writing SQL') and a directive to follow the notes. It also states when to use the intent parameter and when to omit it, which is exactly the when/when-not guidance the dimension asks for.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources