Skip to main content
Glama
keonchennl

GraphDB MCP Server

listGraphs

Retrieve all available graphs in a repository via GraphDB MCP Server, enabling efficient exploration and management of RDF datasets for knowledge graph analysis.

Instructions

List all graphs in the repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'listGraphs' tool: executes SPARQL query to fetch and return list of graphs in the repository.
    } else if (request.params.name === "listGraphs") {
        // Query to get all graphs in the repository
        const query = `
      SELECT DISTINCT ?graph
      WHERE {
        GRAPH ?graph { ?s ?p ?o }
      }
      ORDER BY ?graph
    `;
    
        try {
            const result = await executeSparqlQuery(query);
            return {
                content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
                isError: false,
            };
        } catch (error: any) {
            return {
                content: [{ type: "text", text: `Error listing graphs: ${error.message}` }],
                isError: true,
            };
        }
    }
  • index.ts:418-425 (registration)
    Tool registration in listTools response: defines name, description, and input schema for 'listGraphs'.
    {
        name: "listGraphs",
        description: "List all graphs in the repository",
        inputSchema: {
            type: "object",
            properties: {}
        },
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists graphs but doesn't describe how it behaves—e.g., whether it's read-only, safe, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps in understanding the tool's operational traits.

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, clear sentence with no wasted words. It is front-loaded with the core action and resource, making it highly efficient and easy to understand at a glance.

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

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is minimal but incomplete. It lacks behavioral context, usage guidelines, and output details, which are important even for simple tools. Without annotations or an output schema, the description should do more to inform the agent about what to expect.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't need to add parameter details, as there are none to explain. It efficiently states the tool's purpose without unnecessary parameter information, meeting the baseline for tools with no parameters.

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 clearly states the action ('List') and the resource ('all graphs in the repository'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from the sibling tool 'sparqlQuery', which might also involve graph operations, so it doesn't reach the highest score of 5.

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?

The description provides no guidance on when to use this tool versus the sibling 'sparqlQuery' or any alternatives. It lacks context about use cases, prerequisites, or exclusions, offering only a basic statement of purpose without operational guidance.

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

Related 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/keonchennl/mcp-graphdb'

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