Skip to main content
Glama

complete_product

Destructive

Finalize CvLAC product records by updating keywords, areas, coauthors, recognitions, and linking thesis students. Preview changes with dry_run; deletions require confirm_delete.

Instructions

Complete the post-save CvLAC phase for an existing product. It manages ordered keywords, knowledge areas, coauthors and recognitions; for theses it also links students with their participation. It reads current values, resolves catalogue names, and never removes an existing value without confirm_delete:true. Use dry_run:true to preview catalogue resolution and removals without writing.

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": {
      "section": "<section>",
      "label": "<label>"
    },
    "name": "complete_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
areasNoComplete ordered replacement list of product knowledge areas, by code or name
labelYesExact title as shown in the section list
dry_runNoPreview without creating keywords or submitting lists
sectionYesProduct section containing the existing item
keywordsNoComplete ordered replacement list of product keywords
studentsNoComplete thesis student list; each item may use participation TUT, ASE, COT or ORI
coauthorsNoComplete ordered replacement list of coauthor names; the CvLAC owner is preserved
recognitionsNoComplete ordered replacement list of recognition titles already registered in CvLAC
confirm_deleteNoRequired when the replacement drops existing keywords, areas, coauthors or recognitions, or unlinks thesis students

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses the concrete behavior: it reads current values, resolves catalogue names, and 'never removes an existing value without confirm_delete:true.' It also explains that dry_run previews catalogue resolution and removals without writing, which is exactly the operational detail an agent needs for a destructive tool.

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?

Three sentences, front-loaded with purpose followed by scope and safety semantics; no filler. Slightly dense but every sentence carries information about behavior.

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?

For a destructive mutation tool with no output schema, the description covers scope, ordering semantics, the confirm_delete guard, and the dry_run preview, which is enough to call it correctly. It stops short of describing what a successful run returns, but that is a minor gap given the otherwise thorough coverage.

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 the schema already documents all nine parameters including dry_run and confirm_delete. The description reinforces the dry_run/confirm_delete semantics but adds no syntax or format detail the schema lacks, so the baseline of 3 applies.

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 states a specific verb and scope: 'Complete the post-save CvLAC phase for an existing product,' then enumerates the managed sub-resources (keywords, areas, coauthors, recognitions, thesis students). This is far more than a restatement of the name, though it never explicitly names or contrasts a sibling like update_section.

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?

It gives workflow guidance ('Use dry_run:true to preview...', confirm_delete needed for removals), which tells the agent how to invoke it safely, but it never states when to reach for this tool versus read_cvlac, update_section, or sync. Usage context is implied rather than spelled out.

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