YC GraphQL MCP

Overview Schema Source Related Servers Discussions Admin

yc_get_application

Read-onlyIdempotent

Retrieves a YC application by UUID, including answers and edit flags while omitting login credentials, invitation tokens, and signed media URLs.

Instructions

Read an application by UUID, including answers and edit flags. Omits product login credentials, invitation tokens and signed media URLs.

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": {
      "appUuid": "<appUuid>"
    },
    "name": "yc_get_application"
  }
}

Input Schema

Name	Required	Description	Default
`appUuid`	Yes

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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description earns credit by disclosing redaction behavior the annotations do not: product login credentials, invitation tokens and signed media URLs are deliberately omitted, which tells the agent not to expect those fields. It does not cover permission requirements or not-found behavior, keeping it at 4 rather than 5.

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

Conciseness5/5

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

Two short sentences with no filler; the core action is front-loaded and the exclusion list follows immediately. Every clause carries information an agent would otherwise have to discover empirically.

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?

An output schema exists, so return-value structure need not be described, and the redaction note covers the main surprise an agent could hit. Remaining gaps are minor: no statement about authorization requirements or error/not-found semantics for an invalid or inaccessible UUID.

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?

With one parameter and 0% schema description coverage, the description must carry the burden, and 'by UUID' does confirm the identifier type. However, the schema already specifies format=uuid, a UUID regex and a fixed 36-character length, so the description adds essentially no syntax or constraint detail beyond the structured field.

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?

States a specific verb and resource ('Read an application') plus the lookup key ('by UUID') and enumerates what the payload contains ('answers and edit flags'). It implicitly separates itself from the list-style sibling by requiring a single UUID, but never names an alternative, so it stops short of full sibling differentiation.

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 UUID requirement implies this is the single-record fetch rather than a listing, but there is no explicit when-to-use/when-not guidance and no mention of prerequisites or what to do if the UUID is unknown. Usage is inferable rather than stated.

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