Skip to main content
Glama
Sign In

ToolRouter

by io.github.Humanleap
OverviewDiscussionsAdmin

Add Connector

connector_add

Connect a new OAuth account or MCP server. For OAuth: pass type: "oauth", kind: "slack". For MCP catalog: pass catalog_slug. For custom MCP: pass url + auth_type.

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": "connector_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoMCP server endpoint URL (custom MCP).
kindNoOAuth connector kind (e.g. "slack", "notion"). Required for type: "oauth".
slugNoShort identifier for the connection.
typeNoType of connector to add.
billingNoScope: "personal" (default), "team" (auto-resolves), a team slug, or "team:<id>".
auth_typeNoAuth type (custom MCP). Default: none.
auth_tokenNoAuth token or API key.
header_nameNoCustom header name (for header_key auth).
catalog_slugNoMCP catalog slug for one-click connect.
display_nameNoHuman-readable name (custom MCP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-idempotent write in a closed world. The description adds the mode taxonomy but says nothing about the OAuth interactive/redirect flow, duplicate-connection behavior, or credential storage implications, which are the behaviors an agent most needs here.

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?

Three short sentences, front-loaded with the core purpose followed immediately by the mode-specific parameter routing. Every clause carries information; there is no filler or repetition of the title.

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 10 optional parameters, no required fields, and no output schema, the description covers the critical decision surface: which parameter set applies to which connector type. It omits what happens after invocation (e.g. whether OAuth returns a URL the user must visit) and any required-per-mode callouts, which would make it fully complete.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine value the schema lacks: it groups parameters into coherent combinations per scenario (type+kind for OAuth, catalog_slug for catalog MCP, url+auth_type for custom MCP). It does not clarify billing, slug, or display_name usage, so it stops short of 5.

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?

The description states a specific verb and resource ("Connect a new OAuth account or MCP server") and enumerates the three connection modes, so an agent immediately understands the operation. It does not explicitly contrast itself with adjacent siblings like connector_remove, connector_list, or credential_save, which keeps it 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 Guidelines4/5

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

It gives concrete branching guidance for each mode: OAuth uses type+kind, catalog MCP uses catalog_slug, custom MCP uses url+auth_type. That is clear selection context, but there are no exclusions or explicit "use this instead of X" statements (e.g. versus credential_save for plain API keys).

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

All ToolRouter toolsInspect
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