Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__get_query_description

Retrieve descriptions for one or more TigerGraph queries, including their parameters, to understand query purpose and parameter meanings.

Instructions

Get the description and parameter descriptions of one or more installed queries. Requires TigerGraph 4.0+.

Use When: • Discovering what a query does and what each parameter means • Building query documentation • Understanding a query's parameters together with their descriptions

Quick Start:

{
  "query_name": "getPersonFriends"
}

Tips: • Pass 'all' (the default) to read descriptions for every query • Pair with 'get_query_metadata' to combine parameter types and descriptions • Set descriptions with 'update_query_description'

Related Tools: update_query_description, get_query_metadata, show_query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
graph_nameNoName of the graph. If not provided, uses default connection.
query_nameNoName of the query to read. Pass 'all' (default) to read descriptions for every query.all

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.2

TDQS

A4.7/5.0
Behavior4/5

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

The verb 'Get' clearly indicates a read-only operation with no side effects, and the version requirement is stated. However, with no annotations provided, the description does not explicitly state that no data is modified or that no special authentication beyond the connection profile is required, leaving a small gap in behavioral transparency.

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 well-structured with clear sections: purpose, use cases, quick start, tips, and related tools. It avoids unnecessary filler and each section adds actionable value for an agent.

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?

The description gives sufficient context for calling the tool successfully, including version requirements, default parameter behavior, and related tools. It does not describe the exact output format or error behavior when a query name is not found, but for a simple read operation this is a minor omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have detailed descriptions in the schema, and the tool description adds practical clarification: query_name defaults to 'all', profile and graph_name are optional with fallback behavior. The 'Tips' section further explains how to combine this tool with get_query_metadata for richer parameter information.

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's purpose: to get the description and parameter descriptions of one or more installed queries. It also distinguishes itself from related tools by mentioning get_query_metadata and update_query_description in context.

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

Usage Guidelines5/5

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

The 'Use When' section explicitly lists discovery and documentation scenarios, while 'Quick Start' and 'Tips' provide concrete invocation guidance, including how to use the 'all' default. Related tools are also listed to help agents choose alternatives.

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/tigergraph/tigergraph-mcp'

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