graphql-introspection-mcp

execute_query

Read-only

Run read-only GraphQL queries against an endpoint. Supports variables, authentication, and operation selection.

Instructions

Execute a read-only GraphQL query against the endpoint. Only query operations are allowed.

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": {
      "query": "<query>"
    },
    "name": "execute_query"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	GraphQL query document string
`endpoint`	No	GraphQL endpoint URL (default: http://localhost:5555/graphql)
`password`	No	Password for basic authentication (optional)
`username`	No	Username for basic authentication (optional)
`variables`	No	Variables for the GraphQL operation (optional)
`bearer_token`	No	Bearer token for authentication (optional)
`operation_name`	No	Operation name if document contains multiple operations (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds a behavioral constraint beyond that: 'Only query operations are allowed.' This clarifies that mutations and subscriptions are not permitted, which is not inferable from readOnlyHint alone. The description also confirms the read-only nature, adding value without contradicting the annotation.

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?

The description is a single sentence of about 15 words, front-loaded with the core action ('Execute a read-only GraphQL query'). Every word contributes to defining the tool's purpose and constraints. There is zero redundancy or filler.

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 tool with 7 parameters and no output schema, the description is sufficient for selection and invocation understanding. It specifies the endpoint, operation type, and read-only nature. It doesn't describe return format or authentication details, but those are covered by schema and the general understanding of GraphQL. The sibling context makes the role clear, so a 4 is adequate.

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 input schema has 100% description coverage for all 7 parameters, so the baseline is 3. The description does not elaborate on any parameter meanings beyond what the schema provides. It adds no extra semantic context for parameters like 'query' or 'endpoint', so a score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Execute a read-only GraphQL query against the endpoint.' The verb 'execute' and resource 'GraphQL query' are specific, and the restriction to 'query operations' differentiates it from sibling tools that explore schema (e.g., get_graphql_schema, filter_queries). It is a precise, unambiguous statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: for executing GraphQL queries, while sibling tools are for schema exploration. The statement 'Only query operations are allowed' provides a usage constraint, but it does not explicitly name alternatives or say 'use this instead of X'. The context signals and sibling names make the differentiation clear, earning a score of 4.

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

Deploy Server