Skip to main content
Glama
Sign In
MCP GraphQL Server Multi-Fuente

MCP GraphQL Server Multi-Fuente

by Denisijcu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

register_persisted_query

Persist a GraphQL query and return its hash, enabling reusable queries across multiple data sources.

Instructions

Registra una consulta persistida y devuelve su hash

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": "register_persisted_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesConsulta GraphQL a persistir

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it only says the tool registers and returns a hash. It omits whether registration is idempotent, what permissions it needs, whether the hash is content-derived or server-assigned, and whether an existing query is overwritten.

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

Conciseness4/5

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

A single compact sentence that front-loads the action and the return value with no filler. It is terse to the point of being thin, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no annotations and no output schema, the description at least discloses the return value (the hash), but it leaves out auth, idempotency, and error behavior, so it is only minimally 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?

Schema description coverage is 100% and there is a single required parameter ('query', documented in Spanish as a GraphQL query to persist), so the schema already does the heavy lifting. The description adds no format or constraint detail beyond it.

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?

States a specific verb ('Registra') and resource ('consulta persistida') and discloses the return value ('devuelve su hash'). It is distinguishable from siblings like graphql_query or graphql_mutation, though it never explicitly names an alternative.

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

Usage Guidelines2/5

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

No when-to-use, prerequisites, or alternative-routing guidance is given. An agent cannot tell from the text when persisting a query is preferable to simply calling graphql_query.

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

Deploy Server

Other Tools