Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__update_query_description

Update an installed query's description and optional parameter descriptions to document what it does, making queries self-describing for agents.

Instructions

Set a human-readable description for an installed query and, optionally, descriptions for each of its parameters. Requires TigerGraph 4.0+.

Use When: • Documenting what an installed query does and what its parameters mean • Making queries self-describing for agents and other consumers

Quick Start:

{
  "query_name": "getPersonFriends",
  "query_description": "Return the friends of a given person.",
  "parameter_descriptions": {"personId": "ID of the person to look up"}
}

Tips: • Query must be installed first • Omit 'parameter_descriptions' to set only the query-level description • Read it back with 'get_query_description'

Related Tools: get_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_nameYesName of the installed query to describe.
query_descriptionYesHuman-readable description of what the query does.
parameter_descriptionsNoPer-parameter descriptions, keyed by parameter name (e.g. {"personId": "The id of the person to look up"}).

Schema Changelog

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

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior3/5

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

The description makes clear this is a metadata-updating operation with 'Set', and it notes a runtime version requirement. However, with no annotations provided, it does not disclose overwrite/merge semantics for parameter_descriptions, potential failure behavior if the query is not installed, or what output/return value to expect.

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 organized into Use When, Quick Start, Tips, and Related Tools sections. Each section adds practical value, and there is no redundant or filler content.

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?

It includes the essential prerequisites, an example call, and a related read-back tool, so an agent can invoke it correctly. It could be slightly more complete by stating the expected return value and whether existing parameter descriptions are replaced wholesale, but these are minor gaps for this simple update operation.

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 five parameters are described in the schema, and the prose adds valuable guidance beyond the schema: an example payload, the default connection behavior for profile/graph_name, and the meaning of the parameter_descriptions keys. It also clarifies that omitting parameter_descriptions limits the update to the query-level description.

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?

Clearly identifies the action (Set) and the resource (an installed query's description, plus optional per-parameter descriptions). It is readily distinguished from related tools like get_query_description and install_query by focusing on updating metadata.

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 states when to use the tool: documenting what a query does and what its parameters mean. It also gives prerequisites (query must be installed, TigerGraph 4.0+) and points to get_query_description for reading the description back, helping an agent choose the right 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/tigergraph/tigergraph-mcp'

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