Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__upsert_vectors

Idempotent

Upsert multiple vertices with inline vector data to a specified vertex type and attribute using the REST API. Accepts a list of vertex IDs, vectors, and optional attributes.

Instructions

Upsert multiple vertices with vector data using the REST Upsert API. Vectors must be provided inline as lists of floats (i.e., already in memory). To bulk-load vectors from a local file, use 'load_vectors_from_csv' or 'load_vectors_from_json' instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
vectorsYesList of vectors to upsert, each with vertex_id, vector, and optional attributes.
graph_nameNoName of the graph. If not provided, uses default connection.
vertex_typeYesType of the vertices.
vector_attributeYesName of the vector attribute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide the safety profile (idempotentHint true, destructiveHint false, readOnlyHint false). The description adds the inline-vector constraint and the REST API context, which are genuinely useful behavioral details beyond the annotations. It does not discuss error or response behavior, but annotations cover the core safety aspects.

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 two sentences with no filler. The first sentence states the action and API, the second states a key constraint and points to alternatives. Everything earns its place.

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?

The description, combined with the fully-described schema and safety annotations, gives an agent everything needed to call the tool correctly: the purpose, the data format requirement, and the routing to alternative tools. No output schema exists, so explaining return values is unnecessary.

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 100%, so all five parameters are described in the schema. The description reiterates that vectors must be inline lists of floats, which is a small addition, but it does not introduce any new parameter-level detail beyond what the schema already provides. Baseline of 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 names a specific verb (Upsert), a specific resource (vertices with vector data), and the mechanism (REST Upsert API). It also names the file-based alternatives (load_vectors_from_csv/load_vectors_from_json), making it easy for an agent to distinguish this tool from its siblings.

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?

Explicitly states the condition for using this tool: vectors must already be in memory as lists of floats. It then routes the agent to the alternative tools for file-based bulk loading, leaving no ambiguity about when to choose this over those.

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