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

MCP GraphQL Server Multi-Fuente

by Denisijcu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_sources

Lists all available data sources and shows the currently active one, helping you verify which CSV, Google Sheets, SQLite, PostgreSQL, MySQL, MongoDB, or Oracle source GraphQL queries will use.

Instructions

Lista todas las fuentes de datos disponibles y cuál está activa actualmente

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the return content (all sources plus the currently active one), which is the key trait for a listing tool, but says nothing about ordering, auth requirements, or output format details.

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?

A single front-loaded sentence with no filler; the active-source detail is appended efficiently rather than padding the text.

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 zero-parameter read tool with no output schema, the description is nearly sufficient: it explains what you get back, which is the only thing the schema cannot convey. Minor gaps remain around the shape of the returned source records.

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. There is nothing parameter-related the description could add or omit, and its claim of full scope ("todas las fuentes") correctly signals there is no filtering input.

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 clear verb ("Lista") and resource ("fuentes de datos") plus the scope detail that it also reports which source is active. This is specific enough to distinguish it from siblings like switch_source or get_schema, though it never names an alternative explicitly.

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: an agent can infer this is the discovery step before calling switch_source, but the description states no when-to-use condition, no prerequisites, and no exclusions relative to the sibling tools.

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