Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__update_query_description

Idempotent

Document installed TigerGraph queries by setting query and parameter descriptions to make them self-describing for agents and consumers.

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.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the TigerGraph 4.0+ version requirement and the prerequisite that the query must be installed, which is useful context. It doesn't contradict annotations and adds value beyond them, though it could detail overwrite behavior or error handling more.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with headers (Use When, Quick Start, Tips, Related Tools) and front-loaded with the core action. It is somewhat lengthy but each section serves a purpose, with no redundant sentences.

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

Completeness5/5

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

For a low-complexity tool with no output schema, the description covers prerequisites, optional parameters, and related read-back tool. An agent has everything needed to invoke it correctly.

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?

The schema covers all parameters with descriptions (100% coverage). The description provides a Quick Start example and notes that parameter_descriptions is optional, but it doesn't add significant semantic depth beyond what the schema already provides. Baseline 3 is appropriate.

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 verb ('Set') and resource ('a human-readable description for an installed query') and differentiates from siblings by focusing on the write operation vs. get_query_description and show_query. The purpose is unambiguous and specific.

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?

It includes a 'Use When' section with explicit conditions (documenting queries, making them self-describing) and lists related tools for context. It also provides tips about prerequisites (query must be installed) and how to read back the result, making usage guidance complete.

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