Skip to main content
Glama
Sign In

noback

by app.noback
OverviewDiscussions(1)Admin

connect

Optional: you don't need it, create_app asks for approval by itself the first time you publish. Asks the person for approval without publishing anything (agent is your name, like "Claude Code"). Returns url, code, pollKey and message. Take the person to url yourself: open it in their browser if you can (open on macOS, xdg-open on Linux, start on Windows, or navigate there if you have a browser); if you can't, show them the link in one line in the language of the conversation. Then call connect_status with pollKey and carry on by yourself as soon as it's approved, without asking the person to type anything. Never put pollKey in an app.

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

Input Schema

NameRequiredDescriptionDefault
agentNoYour name as the person knows you (e.g. "Claude Code", "Codex", "ChatGPT").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses side-effect scope (approval only, no publishing), the exact response fields, and a security constraint (never put pollKey in an app). The annotations mark this as non-read-only, which is consistent with creating a pending approval request, so no contradiction. It omits how long the approval/pollKey remains valid, which limits the score to 4.

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?

Every sentence carries operational value. It could be tightened, since the opening clause delays the purpose and the browser-launch instructions are dense, but nothing is filler.

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?

For a one-parameter tool with no output schema, the description covers what is returned (url, code, pollKey, message) and what to do next. An agent has everything needed to call it and complete the approval loop.

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 coverage is 100% and the single parameter is already documented in the schema. The description's "agent is your name, like 'Claude Code'" restates that with an example but adds no new semantics. Baseline 3 applies when the schema carries the parameter meaning.

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 action: request a person's approval without publishing anything, and returns url/code/pollKey/message. It explicitly distinguishes itself from the sibling create_app ("create_app asks for approval by itself the first time you publish"), so an agent can tell why this tool exists separately. It loses a point because the lead-in "Optional: you don't need it" frames purpose as an afterthought rather than a statement of what the tool does.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance (optional; create_app self-approves) plus a full follow-up workflow: open the url in the person's browser, call connect_status with pollKey, and continue without asking the person to type anything. Platform-specific instructions (open/xdg-open/start) make it actionable end to end.

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

All noback toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources