Skip to main content
Glama
friendlygeorge

GraphQL MCP Server

execute_query

Read-onlyIdempotent

Query a GraphQL endpoint with a raw query string and optional variables. Returns the response data field or a structured error message.

Instructions

Send a raw GraphQL query string to the endpoint. Use this when you already have a complete query — for example, one written by a human or copied from API docs. Returns the data field of the response, or a structured error message if the server returned errors. Variables are passed through as-is. Idempotent: same query → same result (for read-only queries).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesGraphQL query string. Example: '{ user(id: 42) { id name email } }'
variablesNoVariables to pass alongside the query. Example: { 'id': 42 }. Use ${varName} in the query to reference them.
operation_nameNoIf the query contains multiple operations, the name of the one to execute.
Behavior4/5

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

Describes return behavior (data field or structured error) and idempotency, adding value beyond annotations. Notes variables are passed through as-is.

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?

Three concise sentences, each with clear purpose. No wasted words.

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?

Covers purpose, usage, behavior, and return structure. Missing mention of endpoint source but sufficient for a query tool.

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?

Schema coverage is 100%, so baseline is 3. Description adds no significant meaning beyond the schema for parameters.

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?

Clearly states 'Send a raw GraphQL query string to the endpoint' with specific verb and resource. Distinguishes from sibling tools like execute_mutation and execute_typed_query.

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?

Explicitly says 'Use this when you already have a complete query' and gives examples. Provides clear context but does not explicitly state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/friendlygeorge/graphql-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server