withHuman

This connector has been deprecated

This is a duplicate of the actual entry deprecating this in favor of the original.

Create gateway server

create_gateway_server

Register an MCP server on the gateway with its first revision and activate it unless activate is false. Agents reach its tools as __, but only the tools set_agent_tool_access grants them, and every call still goes through the approval pipelines. Store an organization-held scope's credential afterwards with set_gateway_scope_headers; an OAuth scope is connected by a person in the app, and a member-held scope by each member on their Connections page.

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": {
      "server_slug": "<server_slug>",
      "name": "<name>",
      "scopes": "<scopes>"
    },
    "name": "create_gateway_server"
  }
}

Input Schema

Name	Required	Description
`url`	No	The downstream server's Streamable HTTP endpoint. Give exactly one of url and tunnel_id.
`name`	Yes	Display name.
`scopes`	Yes	The server's scopes (named credentials), 1 to 20, in the order agents see them. The whole list again on every revision: a scope left out is retired when the revision is activated and its stored credentials are dropped.
`activate`	No	Activate the new revision right away so the gateway serves it from its next configuration poll. Defaults to true.
`tunnel_id`	No	The id of the tunnel the downstream server is reached through (from list_gateway_tunnels), for a server inside your own network. Give exactly one of url and tunnel_id.
`server_slug`	Yes	The server's slug: lowercase letters, digits and dashes. Agents see its tools as <slug>__<tool>. A new slug registers the server and is taken for good, archived servers included.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the first revision is activated unless activate is false, that agents only receive tools granted through set_agent_tool_access, and that every call passes through approval pipelines. It also explains the credential-handling consequences for organization-held, OAuth, and member-held scopes.

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?

The description is three tightly packed sentences with the core creation behavior front-loaded. The remaining sentences add relevant access-control and credential follow-up context without wasting space.

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?

For a complex create tool, the description plus schema covers activation, access control, approval behavior, and credential follow-up well. Since there is no output schema, the description is slightly incomplete about what the create call returns, but it provides enough context to invoke the tool correctly.

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%, so the schema already documents all six parameters in detail. The description reinforces some parameter behavior, especially activation and scope credential modes, but mostly repeats schema-level semantics rather than adding new parameter syntax or constraints.

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 states a specific verb and resource: register an MCP server on the gateway with its first revision and activate it by default. It also distinguishes this creation flow from later revision activation by describing the first-revision behavior and the activation default.

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 gives clear post-creation guidance for credential setup, naming set_gateway_scope_headers for organization-held scopes and explaining how OAuth and member-held scopes are connected. It does not explicitly say when to use this tool versus update_gateway_server or activate_gateway_server_revision, so it stops short of full alternative guidance.

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

All withHuman 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.

Resources

Need Help?