Skip to main content
Glama

add_triples

Import knowledge-graph triples from CSV, Excel, JSON, or JSON lines into a bibliometric run to capture paper methods, data, theories, and findings for analysis.

Instructions

Add knowledge-graph triples from a file (CSV, Excel, JSON or JSON lines) to a run. Columns: paper_id (EID, DOI or title), subject, relation, object (optional: subject_type, object_type, evidence). Paper relations: USES_METHOD, USES_DATA, USES_THEORY, STUDIES, STUDIED_IN, IN_INDUSTRY, AT_LEVEL (subject "PAPER"); findings between constructs: INCREASES, DECREASES, NO_EFFECT_ON, MODERATES, MEDIATES, ASSOCIATED_WITH. The triples join the knowledge graph and answer Q39 (methods, data, theories per theme) and Q40 (findings, contested relations).

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": {
      "run_id": "<run_id>",
      "path": "<path>"
    },
    "name": "add_triples"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.16.1

TDQS

A3.5/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 useful behavior: the accepted file formats, the required and optional columns, and the closed relation vocabulary, and it states that triples join the knowledge graph. It does not say what happens on duplicate or conflicting triples, whether the operation is additive or replacing, whether partial writes occur on validation failure, or what permissions the run requires.

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 front-loaded with the action and source formats before the long relation vocabulary, and every clause about columns and relations earns its place as necessary input validation guidance. The Q39/Q40 references are opaque to an agent that cannot see the question list, but they are a single trailing clause rather than padding.

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?

An output schema exists, so return values need no explanation here, and the description covers the genuinely complex part: file format, required columns, and the legal relation vocabulary. For a mutation tool with zero annotations, the remaining gaps are write semantics (idempotency, duplicate handling, failure behavior) rather than anything about what data to supply.

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 0% and the two parameters are bare strings, so the description must compensate. It does so partly: 'from a file' implies path is a file location and 'to a run' implies run_id targets an existing run, and the column list tells the agent what must be inside the file. It still omits path format conventions (absolute vs relative, server-side staging) and any run_id validity constraints.

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?

The description names a specific verb and resource (add knowledge-graph triples) plus the accepted source formats (CSV, Excel, JSON, JSON lines) and the destination (a run). It does not explicitly contrast itself with the closely-named siblings extract_triples and save_triples, which share the same resource, so an agent must infer the file-ingestion distinction from the format list alone.

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 implied rather than stated: an agent can infer this is the path for loading an already-prepared triple file, and the mention of Q39/Q40 indicates the analytical payoff. There is no explicit when-not guidance, no prerequisites (does the run need to exist first? must the file be staged server-side?), and no routing between this tool and other triple-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.