YC GraphQL MCP

Overview Schema Source Related Servers Discussions Admin

yc_status

Read-onlyIdempotent

Check transport mode, local authentication or browser pairing, outstanding work, and mutation policy without making a YC request.

Instructions

Transport mode, local authentication or browser pairing, outstanding work, and mutation policy. Makes no YC request.

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_status"
  }
}

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds one genuinely useful fact beyond that — that no YC request is issued, i.e. it is a purely local probe despite openWorldHint — but it does not clarify what 'outstanding work' covers, whether auth state requires credentials to report, or how fresh the policy information is.

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 most operationally relevant fact ('makes no YC request') is placed last for emphasis. The opening is a bare list of nouns rather than a stated action, which slightly weakens front-loading.

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?

An output schema exists, so return values need no explanation here, and the parameter surface is empty. What remains missing is guidance on when an agent should call this versus yc_connection, and any hint about cost or side effects of polling it repeatedly.

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 the baseline is 4 and there is nothing for the description to disambiguate. The schema is an empty, closed object, consistent with a no-argument status call.

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 enumerates the specific state this tool surfaces: transport mode, local authentication vs. browser pairing, outstanding work, and mutation policy. That content list is distinctive enough to separate it from siblings like yc_connection or yc_list_operations, but it is a verbless noun phrase that never explicitly says it returns a status report.

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?

The phrase 'Makes no YC request' implies this is a cheap, local, safe probe, which nudges an agent toward calling it before or instead of network-backed tools. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative for checking connection state versus operation state.

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