SocialGPT

Server info

server_info

Read-only

Return this server's identity and capabilities: its name, version, the surface label (public-read-v1), and the full list of OAuth scopes it supports. Useful as a connectivity / capability check before calling scoped tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	Yes
`scopes`	Yes	All OAuth scopes this server supports.
`surface`	Yes	The tool-surface label, e.g. 'public-read-v1'.
`version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 24, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Output of `server_info`."

addedOutput schema / properties

Added value: +{
+  "name": {
+    "type": "string"
+  },
+  "scopes": {
+    "description": "All OAuth scopes this server supports.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "surface": {
+    "description": "The tool-surface label, e.g. 'public-read-v1'.",
+    "type": "string"
+  },
+  "version": {
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "name",
+  "version",
+  "surface",
+  "scopes"
+]

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value by listing the returned fields (name, version, etc.) and the purpose, going beyond annotations.

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 with no wasted words. The purpose and return values are front-loaded, making it easy for an AI to parse.

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?

Given no parameters, clear annotations, and the presence of an output schema, the description fully covers the tool's behavior and return value context.

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?

The tool has zero parameters, so the description does not need to add parameter meaning. Baseline 4 applies per guidelines.

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 specifies exactly what the tool returns: server name, version, surface label, and OAuth scopes. It also states it's for a connectivity/capability check, clearly distinguishing it from siblings like whoami.

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 explicitly says 'Useful as a connectivity / capability check before calling scoped tools,' providing clear when-to-use context. It does not list alternatives, but the intent is clear.

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

All SocialGPT tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.