Skip to main content
Glama

protogrid

by dev.protogrid
OverviewDiscussionsAdmin

Get a connection block

get_connection
Read-onlyIdempotent

Minimal connection block for the preferred remote (or package) with ${SECRET} placeholders, formatted for a target client. Secrets are never accepted or returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOfficial reverse-DNS name
targetNoOutput format (default mcpServers)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesSuggested name for the server in the client configuration
kindYes
classYesR0 remote no auth, R1 static secret, R2 OAuth, L0 local package
serverYes
targetYes
secretsYesPlaceholders to replace with values you hold
autonomousYes
connectionYesThe block for the target client: an object for JSON targets, a string for text ones
human_stepsYes
content_typeYes
next_actionsYesFollow-up calls: action is the tool, arguments are ready to pass ({placeholders} are yours to fill)
placeholdersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "autonomous": {
+      "type": "boolean"
+    },
+    "class": {
+      "description": "R0 remote no auth, R1 static secret, R2 OAuth, L0 local package",
+      "enum": [
+        "R0",
+        "R1",
+        "R2",
+        "L0",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "connection": {
+      "description": "The block for the target client: an object for JSON targets, a string for text ones"
+    },
+    "content_type": {
+      "enum": [
+        "application/json",
+        "text/plain"
+      ],
+      "type": "string"
+    },
+    "human_steps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "key": {
+      "description": "Suggested name for the server in the client configuration",
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "remote",
+        "package",
+        "bundle"
+      ],
+      "type": "string"
+    },
+    "next_actions": {
+      "description": "Follow-up calls: action is the tool, arguments are ready to pass ({placeholders} are yours to fill)",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "action": {
+            "type": "string"
+          },
+          "arguments": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          }
+        },
+        "required": [
+          "action"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "placeholders": {
+      "type": "string"
+    },
+    "secrets": {
+      "description": "Placeholders to replace with values you hold",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "where": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "where"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "server": {
+      "type": "string"
+    },
+    "target": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "server",
+    "key",
+    "kind",
+    "class",
+    "autonomous",
+    "human_steps",
+    "target",
+    "content_type",
+    "connection",
+    "secrets",
+    "placeholders",
+    "next_actions"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / properties / target / enum
      Previous value: -[
-  "mcpServers",
-  "vscode",
-  "cursor",
-  "claude-code-cli",
-  "codex-toml",
-  "gemini",
-  "goose"
-]New value: +[
+  "mcpServers",
+  "vscode",
+  "cursor",
+  "claude-code-cli",
+  "codex-toml",
+  "opencode",
+  "gemini",
+  "goose"
+]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral value beyond them: secrets are never accepted or returned, and secrets appear as ${SECRET} placeholders in the output. This tells the agent it cannot round-trip credentials, which is actionable context.

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?

A single dense sentence with zero filler. The distinctive constraint (secret placeholders) and the output-shaping purpose (formatted for a target client) are both front-loaded.

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

Completeness4/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 the annotation set covers safety behavior. The description supplies the one thing structured fields cannot: the ${SECRET} placeholder convention and the no-secrets guarantee. Only the missing sibling routing keeps it short of 5.

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 description coverage is 100% and both parameters are documented there (name as reverse-DNS, target as output format with an enum and default). The description adds only a light gloss ('preferred remote (or package)', 'target client') and no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: it generates a minimal connection block for a preferred remote/package, formatted for a target client, with ${SECRET} placeholders. That is clearly distinguishable from siblings like get_server (raw server info) and check_server (health check), though it does not name them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied — the mention of a 'preferred remote (or package)' and 'target client' hints at when it is useful, but there is no explicit when-to-use or when-to-prefer-this-over-get_server guidance. Nothing misleading, but the agent must infer the selection context.

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

All protogrid toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources