Skip to main content
Glama

get_graph_list

Get a clean list of named graphs from a SPARQL endpoint, with internal graphs filtered out. Supports ranking by database name for endpoints hosting multiple databases.

Instructions

Get a list of named graphs on a SPARQL endpoint. Virtuoso/OpenLink internal graphs are filtered out. If database is given, graph URIs containing that substring (case-insensitive) are ranked first — useful when the endpoint hosts multiple databases (e.g. SIB hosts UniProt + Rhea + Bgee + OMA). For a database not yet in the registry, pass endpoint_url (or endpoint_name if its parent endpoint is registered) to bypass database validation; database can still be supplied alongside as a ranking hint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseNoRDF database name (e.g. 'uniprot', 'chembl'). When the name is in the registry it resolves the endpoint URL; in any case the value is used as a case-insensitive substring to rank matching graph URIs first. Optional if `endpoint_url` or `endpoint_name` is provided.
endpoint_nameNoShort endpoint name (e.g. 'primary', 'sib', 'ebi'). Use when the database is not yet registered but its parent endpoint is.
endpoint_urlNoDirect SPARQL endpoint URL. Use when neither the database nor its parent endpoint name is in the registry.
include_systemNoIf True, include Virtuoso/OpenLink internal graphs (virtrdf, ldp, activitystreams, etc.). Default False — these are never useful for queries.
dbnameNo
dbNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses filtering of internal graphs, ranking by database substring, and validation bypass with endpoint_url/name. Missing details on rate limits, auth, or idempotency, but these are less critical for a read-only list tool.

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?

Single paragraph with front-loaded purpose, followed by essential details. Every sentence adds value. No redundancy or irrelevant content.

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?

Overall informative, but lacks explanation for the undocumented parameters (dbname, db) and does not reference sibling tools for context (e.g., find_databases for registry lookups). Output schema exists to cover return format, so omission is acceptable.

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 67% (4 of 6 parameters have descriptions). The description adds significant meaning for database, endpoint_name, endpoint_url, and include_system (ranking, filtering logic). However, it ignores dbname and db parameters, which lack schema descriptions, creating a gap.

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 retrieves a list of named graphs from a SPARQL endpoint, distinct from sibling tools like get_sparql_endpoints (endpoint list) and run_sparql (query execution). The verb 'Get' and resource 'list of named graphs' specify the action and output.

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?

Provides detailed guidance on parameter usage (database, endpoint_url, endpoint_name) and ranking behavior. Explicitly explains when to use each parameter combination. However, does not contrast with sibling tools or state when not to use this tool.

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/dbcls/togomcp'

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