YC GraphQL MCP

Overview Schema Source Related Servers Discussions Admin

yc_connection

Read-onlyIdempotent

Retrieve direct HTTP setup details or browser-extension pairing configuration to connect MCP clients, while keeping pairing tokens private and never returning YC credentials.

Instructions

Direct HTTP setup information, or local extension pairing configuration in browser mode. Never returns YC credentials. Keep browser pairing tokens private.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`untrustedContent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Nov 12, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-derivable context: an explicit guarantee that YC credentials are never returned and a handling warning that browser pairing tokens must be kept private — both security-relevant facts an agent would otherwise not know.

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?

Two short sentences with no filler, and the mode distinction is front-loaded ahead of the security caveats. It is slightly telegraphic — 'Direct HTTP setup information' is a fragment that could be a clause — but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with an output schema and rich annotations, the definition covers the essentials: what it returns and two safety constraints. The remaining gap is contextual framing — what 'direct HTTP' mode means versus browser pairing, and when an agent should reach for this — which the description leaves implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is 100% and the additionalProperties:false empty object leaves no ambiguity to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two distinct things it surfaces — 'Direct HTTP setup information' and 'local extension pairing configuration in browser mode' — so an agent can infer it returns connection/pairing setup data. But it is a bare noun phrase with no verb, and neither 'YC connection' nor 'direct HTTP setup' is defined, leaving the exact resource ambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no reference to any sibling tool (e.g. yc_status or yc_get_application) that might be the better call. The only conditional hint is 'in browser mode', which describes a mode rather than telling the agent when to select this tool.

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