Skip to main content
Glama

Get a server descriptor

get_server
Read-onlyIdempotent

Official server.json plus connectability (class, remotes with auth/health, packages), current tools, trust breakdown and identity for one server name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOfficial reverse-DNS name, e.g. io.github.acme/acme-mcp
schemasNoInclude tool input/output schemas (default false; use list_tools for full schemas)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_metaYesprotogrid enrichment next to the official registry metadata
serverYesThe official server.json as published
next_actionsYesFollow-up calls: action is the tool, arguments are ready to pass ({placeholders} are yours to fill)

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": {
      +    "_meta": {
      +      "additionalProperties": {},
      +      "description": "protogrid enrichment next to the official registry metadata",
      +      "properties": {
      +        "dev.protogrid/connectability": {
      +          "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"
      +            },
      +            "human_steps": {
      +              "items": {
      +                "type": "string"
      +              },
      +              "type": "array"
      +            },
      +            "packages": {
      +              "description": "Packages with runtime hint and required secrets",
      +              "items": {
      +                "additionalProperties": {},
      +                "properties": {},
      +                "type": "object"
      +              },
      +              "type": "array"
      +            },
      +            "remotes": {
      +              "description": "Remotes with transport, auth, protocol and health",
      +              "items": {
      +                "additionalProperties": {},
      +                "properties": {},
      +                "type": "object"
      +              },
      +              "type": "array"
      +            }
      +          },
      +          "required": [
      +            "class",
      +            "autonomous",
      +            "human_steps",
      +            "remotes",
      +            "packages"
      +          ],
      +          "type": "object"
      +        },
      +        "dev.protogrid/identity": {
      +          "additionalProperties": {},
      +          "properties": {
      +            "canonical_id": {
      +              "type": "string"
      +            },
      +            "owner": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "verified": {
      +                  "type": "boolean"
      +                }
      +              },
      +              "required": [
      +                "verified"
      +              ],
      +              "type": "object"
      +            }
      +          },
      +          "required": [
      +            "canonical_id",
      +            "owner"
      +          ],
      +          "type": "object"
      +        },
      +        "dev.protogrid/quality": {
      +          "additionalProperties": {},
      +          "properties": {
      +            "checks": {},
      +            "label": {
      +              "type": "string"
      +            },
      +            "score": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "score",
      +            "label",
      +            "checks"
      +          ],
      +          "type": "object"
      +        },
      +        "dev.protogrid/tools": {
      +          "description": "Current tools; schemas only with schemas=true",
      +          "items": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "name": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "name"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "dev.protogrid/trust": {
      +          "additionalProperties": {},
      +          "properties": {
      +            "blocked": {
      +              "type": "boolean"
      +            },
      +            "flags": {
      +              "items": {
      +                "type": "string"
      +              },
      +              "type": "array"
      +            },
      +            "score": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "score",
      +            "flags",
      +            "blocked"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "dev.protogrid/connectability",
      +        "dev.protogrid/tools",
      +        "dev.protogrid/trust",
      +        "dev.protogrid/quality",
      +        "dev.protogrid/identity"
      +      ],
      +      "type": "object"
      +    },
      +    "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"
      +    },
      +    "server": {
      +      "additionalProperties": {},
      +      "description": "The official server.json as published",
      +      "properties": {},
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "server",
      +    "_meta",
      +    "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. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context: the result includes auth/health status for remotes, trust breakdown, and identity, which tells the agent this is a rich inspection call rather than a simple existence check.

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?

A single dense sentence that front-loads the primary output (server.json) and then lists the supplementary payloads. Every clause carries information, though the parenthetical is slightly crammed.

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?

With an output schema present, the description need not enumerate return fields, yet it does so helpfully. Combined with full schema coverage and rich annotations, an agent has enough to invoke this correctly; only the lack of sibling routing guidance is missing.

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 (name, schemas) are documented in the schema, including the reverse-DNS format and the note to use list_tools for full schemas. The description adds no additional parameter-level 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 resource (the official server descriptor for one server name) and enumerates the payload categories it returns: server.json, connectability, tools, trust breakdown, identity. This is clearly more than a restatement of the name. It does not, however, explicitly differentiate itself from the sibling check_server, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus check_server, get_connection, or search. The usage is only implied by the list of returned content, and the agent must infer whether this is a cheap lookup or an expensive full fetch.

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