@cocaxcode/database-mcp

Overview Schema Source Related Servers Discussions Admin

conn_group_add_scope

Add a directory to a connection group so its connections become accessible from that directory. Provide the group name and optional path, defaulting to the current directory.

Instructions

Añade un directorio (scope) a un grupo. Las conexiones del grupo seran accesibles desde ese directorio.

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": {
      "group": "<group>"
    },
    "name": "conn_group_add_scope"
  }
}

Input Schema

Name	Required	Description	Default
`group`	Yes	Nombre del grupo
`scope`	No	Ruta del directorio. Si se omite, usa el directorio actual

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Aug 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the group's connections become accessible from the added directory, which is a key behavioral outcome. However, it omits prerequisites (e.g., group must exist, directory path validity), potential errors, reversibility, or idempotency.

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?

Two sentences, front-loaded with the verb and action, no wasted words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple additive operation with complete schema coverage, the description is mostly adequate. However, without annotations or an output schema, it lacks details on error conditions, return values, or side effects. It covers the core purpose but leaves room for more context.

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% with both parameters described. The description adds minimal semantic value beyond the schema, mainly rephrasing 'directorio' as 'scope' and reinforcing the default behavior of omitting scope. Baseline of 3 is appropriate since schema already fully documents parameters.

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 clearly states the action: adds a directory (scope) to a group, and explains the functional consequence (connections become accessible from that directory). It distinguishes from the sibling conn_group_remove_scope by its additive nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage: use when you need to add a scope to a group. It does not explicitly mention alternatives or exclusions, but the purpose is straightforward and the sibling existence is implicit. Lacks explicit when-not-to-use guidance.

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