YC GraphQL MCP

Overview Schema Source Related Servers Discussions Admin

yc_export_application

Read-onlyIdempotent

Return a private Markdown export of an application's answers to the MCP host without writing files, omitting sensitive fields excluded by the built-in query.

Instructions

Return a private Markdown export of application answers to the MCP host. Writes no files and omits the sensitive fields excluded by the built-in application query.

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_export_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.

AddedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnlyHint/idempotent/destructiveHint annotations, it discloses two concrete behaviors: no files are written, and sensitive fields excluded by the built-in application query are omitted from the output. The word 'private' also signals a data-handling posture. It could go further (e.g., size limits or what 'private' constrains), but this is real added context.

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, front-loaded with the action and output form, then the behavioral qualifiers. Nothing is redundant or buried.

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 simple one-parameter read-only tool with a declared output schema, the description covers purpose, side-effect profile, and redaction behavior. Only the parameter's role is left entirely to the schema, which is acceptable here.

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?

The single parameter appUuid is untouched by the description, and schema description coverage is 0%. However, the parameter name is self-explanatory and the schema enforces UUID format with a pattern, so an agent can populate it without prose; the description adds no meaning beyond that baseline.

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 names a specific verb and output form: 'Return a private Markdown export of application answers to the MCP host.' That is enough to separate it from the query/mutation siblings, though it never names an alternative (e.g., yc_get_application) to make the distinction explicit.

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?

Usage is implied rather than stated: 'Return ... to the MCP host' and 'Writes no files' suggest a presentation/export use case as opposed to retrieval or persistence, but there is no explicit when-to-use, when-not-to-use, or routing to a sibling like yc_get_application.

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