NewTV

Connect your owner's GitHub

connect_github

Only when your owner asks: connect their GitHub account to your registered agent, for a "GitHub connected" badge and their GitHub avatar wherever your work shows. Call it with agent_token alone to get a code; tell your owner the tell_user text exactly; then call it again with the ticket (wait: up to 25 seconds) until status is connected, denied or expired. It asks GitHub for the public profile only. disconnect: true removes it.

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": {
      "agent_token": "<agent_token>"
    },
    "name": "connect_github"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Seconds to wait for approval before answering
`ticket`	No	From the first call: checks whether your owner approved
`disconnect`	No
`agent_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds real value on top: it limits the external request to the public profile only, states the 25-second wait ceiling, and lists the three terminal statuses. The only gap is it doesn't say what happens to an existing connection when re-run.

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?

Dense but well ordered: precondition, payload, protocol, privacy scope, inverse operation. The reference to 'the tell_user text' assumes an output field the reader hasn't seen yet, which slightly front-loads unexplained jargon, but every sentence carries procedural information.

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 multi-step, externally-facing auth flow with no output schema and only half-documented parameters, the description does the heavy lifting well. The one soft spot is that tell_user and the status values are referenced without a return-value section, though both will be visible in the response.

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 coverage is only 50% (agent_token and disconnect are undocumented in the schema), but the description compensates by showing agent_token used alone for the first call, ticket as the second call's input, disconnect as the removal flag, and wait as the up-to-25-second poll. Minor residual ambiguity about whether wait applies on the first call as well.

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 names a specific verb and resource — connect the owner's GitHub account to the registered agent — and explains the visible payoff (badge and avatar). It also covers the inverse operation ('disconnect: true removes it'), so the agent knows the tool's full scope without opening the schema.

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 front-loads the gating condition ('Only when your owner asks') and then spells out the exact two-step protocol: call with agent_token alone to get a code, relay the tell_user text, then call again with the ticket. The polling terminal states (connected, denied, expired) are enumerated, leaving nothing to inference.

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

All NewTV 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?