Skip to main content
Glama
Sign In
VeritasGraph

VeritasGraph

by bibinprathap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

veritasgraph_structured_get_term

Retrieve a structured business term by ID or name to view its definition, synonyms, and status.

Instructions

One structured-data business term by id or name, with definition, synonyms and status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "veritasgraph_structured_get_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the return payload (definition, synonyms, status) and that lookup is read-only by implication, but says nothing about not-found behavior, whether name matching is exact or fuzzy, or ambiguity handling when a name matches multiple terms.

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?

A single front-loaded sentence with no filler; the resource, lookup key, and returned fields all appear before any padding would.

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?

For a one-parameter read tool with no output schema, the description covers the essentials, but the absence of annotations and of any not-found or matching-behavior note leaves gaps an agent would hit on a failed or ambiguous lookup.

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

Parameters4/5

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

Schema coverage is 0% and the schema only declares a bare string, so the description's 'by id or name' is the sole source of meaning about what the term parameter accepts. It adds real value, though it does not specify format or matching rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('structured-data business term') and retrieval mode ('by id or name'), and the 'structured-data' qualifier distinguishes it from the sibling veritasgraph_get_term. It does not explicitly name that sibling, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the 'structured-data' qualifier hints at when this applies versus the plain get_term, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the routing.

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