Skip to main content
Glama

sp_prepare_uvyazka_link

Read-only

Prepare a save_structure_analysis payload that links a verified normative snapshot to a Uvyazka project without mutating it, validating source bytes and revision on save.

Instructions

Prepare a save_structure_analysis payload; no project mutation. project_source: registered doc_id, sha256 and optional physical PDF page_number. Use verification_id returned by checking this exact snapshot. Clause must resolve uniquely. Uvyazka validates project membership, original source bytes and optimistic revision on save. Norm source and project source stay separate; requirements remain unapproved.

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_prepare_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 cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), and the description adds real value on top: it warns that validation (project membership, original source bytes, optimistic revision) happens later at save time, not here. It also discloses domain invariants the agent could not guess, namely that norm source and project source stay separate and requirements remain unapproved.

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 key non-mutation guarantee is front-loaded in the first clause, and the rest is packed into short fragments with no filler. The telegraphic, note-like phrasing ('Norm source and project source stay separate') costs a little readability, but every line carries information.

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 prepare/build tool with a nested object parameter and no output schema, the description covers the intent, the no-mutation guarantee, and the verification prerequisite, which is the core of correct invocation. It omits what the prepared payload contains and how expected_revision and snapshot_id relate to the snapshot being verified, leaving meaningful gaps.

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 there are 7 parameters, so the description carries the burden; it explains project_source contents (doc_id, sha256, optional page_number), the origin and purpose of verification_id, and the uniqueness constraint on clause. It leaves project_id, snapshot_id, reason, and expected_revision entirely unexplained, including what the revision is compared against.

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: prepare a save_structure_analysis payload, and explicitly says it causes no project mutation, which separates it from the attach/save path. It stops short of naming the sibling that actually performs the mutation, so an agent must infer the pairing from the 'no project mutation' clause.

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?

Gives one concrete prerequisite ('Use verification_id returned by checking this exact snapshot') and a validity condition ('Clause must resolve uniquely'), which tells the agent how to make a successful call. It never says explicitly when to use this instead of sp_attach_uvyazka_link or what to do when a clause does not resolve uniquely; the two-step relationship is only implied.

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