gurixandClaude
d220c27b67
Add comprehensive proposal for general GraphQL tools in MCP server: - proposal.md: Problem statement and impact analysis - tasks.md: Implementation checklist - specs/mcp-integration/spec.md: 3 new MCP tool requirements - specs/graphql-api/spec.md: GraphQL introspection requirement Proposal introduces get_graphql_schema and execute_graphql_query tools to enable AI agents to discover and interact with the GraphQL API dynamically for complex tasks beyond dedicated member tools. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: GraphQL Introspection Support
|
|
The GraphQL API SHALL support introspection queries that enable clients to discover the complete schema dynamically.
|
|
|
|
#### Scenario: Introspection query returns schema types
|
|
- **GIVEN** the GraphQL API is running
|
|
- **WHEN** a client executes an introspection query for `__schema`
|
|
- **THEN** the response SHALL include all types defined in the schema
|
|
- **AND** include queries, mutations, and object types
|
|
- **AND** include field names, types, and descriptions
|
|
|
|
#### Scenario: Introspection query returns type details
|
|
- **GIVEN** the GraphQL API is running
|
|
- **WHEN** a client executes an introspection query for `__type(name: "Member")`
|
|
- **THEN** the response SHALL include complete Member type details
|
|
- **AND** include all fields with their types
|
|
- **AND** include field descriptions where defined
|
|
|
|
#### Scenario: Introspection is enabled by default
|
|
- **GIVEN** the Strawberry GraphQL schema is configured
|
|
- **WHEN** the schema is created
|
|
- **THEN** introspection SHALL be enabled
|
|
- **AND** the `__schema` and `__type` queries SHALL be available
|