Skip to main content
Glama

Set many descriptions

set_descriptions
DestructiveIdempotent

Write the team's descriptions and synonyms for up to 200 tables and columns in one call, for example when the user asks you to document a whole table or schema. Each item works like set_description. All items are saved together, or none if a table or column does not exist in get_schema, and the error lists which. Show the user what you plan to write before calling it. Changes what every AI tool and person on this connection reads, and is recorded in SaturnSQL with your name. Only make it when the user asked for it or confirmed it. Needs the write scope, the connection's owner or an admin, and a plan that includes Context.

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>",
      "items": "<items>"
    },
    "name": "set_descriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
connectionIdYesConnection id from list_connections.

Output Schema

NameRequiredDescriptionDefault
itemsNo

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?

Goes well beyond the annotations: it discloses atomicity ("All items are saved together, or none"), failure reporting ("the error lists which"), blast radius ("Changes what every AI tool and person on this connection reads"), audit trail ("recorded in SaturnSQL with your name"), and the exact authorization requirements (write scope, owner/admin, plan with Context). These are precisely the traits an agent needs before committing a destructive batch write.

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?

The purpose and trigger are front-loaded and every sentence carries operational content. It is dense to the point of near-run-on, and the pre-call preview instruction partially overlaps with the later "Only make it when the user asked for it or confirmed it" sentence, costing a little tightness.

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?

For a destructive, batched mutation this covers purpose, atomicity, validation failure mode, auth/resource requirements, audit logging, and user confirmation. With annotations declaring destructive/idempotent and an output schema present, nothing material is left for the agent to guess.

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 50%, and the schema already describes the nested item fields, so the description does not need to carry them alone. It adds useful semantics at the batch level — the 200-item ceiling and the item-level equivalence to set_description — but says nothing extra about connectionId or the replace-vs-merge behavior of synonyms, which matters for this call.

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 with scope: "Write the team's descriptions and synonyms for up to 200 tables and columns in one call." It also distinguishes itself from the single-item sibling by noting "Each item works like set_description," so an agent can tell batch from singleton without opening a schema.

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 an explicit trigger ("when the user asks you to document a whole table or schema") and an explicit prerequisite workflow ("Show the user what you plan to write before calling it" and "Only make it when the user asked for it or confirmed it"). The relationship to set_description implies the single-item alternative, and the guidance is unambiguous about when not to act.

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