YC GraphQL MCP

Overview Schema Source Related Servers Discussions Admin

yc_list_applications

Read-onlyIdempotent

List applications in the authenticated account with summaries and edit flags to review application status and identify editable items.

Instructions

List applications in the authenticated account with summaries and edit flags. Uses an observed YC operation; does not depend on introspection.

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

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description adds the authenticated-account scoping and the 'summaries and edit flags' content hint, but the second sentence about 'observed YC operation' and 'introspection' is implementation jargon that tells an agent nothing actionable about behavior, pagination, or result size.

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

Conciseness3/5

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

The first sentence is tight and front-loaded. The second sentence is opaque filler that consumes roughly half the description without changing how an agent would call the tool.

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?

With an output schema present and rich annotations, the description need not explain return values or safety. For a zero-parameter read, the key facts (scope, list vs get) are present; only guidance about result volume or routing to yc_get_application is missing.

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 clarify. The scope statement ('authenticated account') is the only parameter-like constraint and it is already stated.

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 gives a specific verb and resource ('List applications') plus scope ('in the authenticated account') and states what comes back ('summaries and edit flags'). It is distinguishable from yc_get_application by being a listing rather than a single-record fetch, though it never explicitly contrasts with the siblings.

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 only implied by the word 'List' and the account scope; there is no explicit statement of when to prefer this over yc_get_application or yc_query, and no preconditions or exclusions are given. An agent can infer the basic case but must guess at the boundaries.

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