Skip to main content
Glama

sp_attach_uvyazka_link

Attaches unapproved normative evidence to a selected Uvyazka project through MCP using exact project, document, and SHA data; updates only the versioned analysis, not accepted facts or geometry.

Instructions

Save unapproved normative evidence to the selected Uvyazka project via its MCP. Requires configured Uvyazka command and exact project/doc/SHA from Uvyazka. Prepares the same payload as sp_prepare_uvyazka_link. Existing analyses need their revision. Changes only a versioned project analysis, never accepted engineering facts or model geometry.

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": {
      "project_id": "<project_id>",
      "project_source": "<project_source>",
      "snapshot_id": "<snapshot_id>",
      "verification_id": "<verification_id>"
    },
    "name": "sp_attach_uvyazka_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
clauseNo
reasonNo
project_idYes
snapshot_idYes
project_sourceYes
verification_idYes
expected_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, and the description adds real scope information beyond them: it changes only a versioned project analysis and never accepted engineering facts or model geometry. It also notes the revision requirement for existing analyses. It stops short of saying whether the save is reversible or how conflicts are reported.

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?

Four short sentences, front-loaded with the action and followed by prerequisites, relationship to the prepare tool, and side-effect scope. No filler, though the last constraint sentence could be merged with the prerequisite line for tighter flow.

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 mutating tool with no output schema and 0% documented parameters, the description does well on effect scope and prerequisites but is thin on arguments and silent on what a successful call returns or how errors surface. An agent knows what will be touched but not fully what to pass.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, including a free-form nested project_source object, so the description must carry the burden and largely does not. It implies project/doc/SHA identifiers and expected_revision ("existing analyses need their revision") but leaves verification_id, clause, reason, and the internal shape of project_source entirely undefined.

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 verb and resource ("Save unapproved normative evidence to the selected Uvyazka project") and ties it to the sibling sp_prepare_uvyazka_link by saying it prepares the same payload. The domain term "Uvyazka" and "normative evidence" are not explained, but the action is distinguishable from the read/prepare siblings.

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

Usage Guidelines4/5

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

Gives concrete preconditions: a configured Uvyazka command and exact project/doc/SHA obtained from Uvyazka, plus the note that existing analyses need their revision. It also points to sp_prepare_uvyazka_link as the payload-equivalent step, though it never states when not to use this tool or what to do on failure.

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