Skip to main content
Glama

Connect the full Gloam agent

gloam_connect_full_agent
Read-onlyIdempotent

Commands to install the local Gloam MCP server, which can sign and pay (shield, private pay, x402 and MPP, spending limits) with keys kept on your machine: Claude Code, Codex, Cursor, VS Code, Claude Desktop and any MCP client, plus the plugin marketplace gloamtrade/gloam-plugins.

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

Input Schema

NameRequiredDescriptionDefault
clientNoWhich app to show commands for.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: keys stay on the user's machine, the server can sign and pay (shield, private pay, x402 and MPP, spending limits), and a plugin marketplace is involved. It still does not say what the returned commands look like or whether the user must run them manually, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence and front-loads the point, which is good. However, it is a run-on that packs a client enumeration, a feature list in parentheses, and a marketplace reference into one clause, so it reads more like marketing copy than a crisp tool contract.

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 one-parameter, read-only helper with no output schema, the description conveys what the tool produces (commands) and its scope (which clients, what capabilities the resulting server has). The remaining gap is output format and whether commands are meant to be executed by the agent or pasted by the user.

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% with a single enum parameter complete with default 'all', so the schema fully documents the input. The description never mentions the client parameter, the 'all' default, or the gemini value, adding no meaning beyond the schema. 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?

The description states what the tool returns: installation commands for a local Gloam MCP server, enumerating supported clients (Claude Code, Codex, Cursor, VS Code, Claude Desktop) and mentioning the plugin marketplace. That is a specific verb+resource. It falls short of 5 because the opening phrase 'Commands to install...' is slightly ambiguous about whether the tool installs anything or only emits command text, and it does not distinguish itself from siblings like gloam_info or gloam_mpp_how_to.

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: an agent can infer this is the setup/onboarding tool for connecting an MCP client, and the client list hints at the scope of use. There is no explicit when-to-use statement, no mention of when to prefer gloam_info or gloam_mpp_how_to, and no note that the output is meant to be handed to the user to run.

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.