sprinty

Overview Schema Source Related Servers Discussions Admin

artifact_add

Attach a file path to a sprint and optionally link it to specific item IDs to keep sprint artifacts organized and traceable.

Instructions

Attach a file path to the sprint, optionally related to item ids.

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": {
      "title": "<title>",
      "path": "<path>"
    },
    "name": "artifact_add"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No
`path`	Yes
`title`	Yes
`agent_token`	No
`description`	No
`related_items`	No
`client_agent_id`	No
`claim_generation`	No
`client_session_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.2Oct 23, 2026

addedInput schema / properties / agent_token

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / claim_generation

Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / client_agent_id

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / client_session_id

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

First observedv0.1.9Jun 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It implies a write operation by saying 'Attach,' but does not explain permissions, duplicate handling, path validation, idempotency, or what happens when related item ids are invalid.

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 a single front-loaded sentence with no wasted text. However, it is extremely terse for a nine-parameter mutation tool, so the brevity comes at the cost of needed detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given nine parameters, no annotations, no output schema, and no schema descriptions, the description is too sparse. It states the main action but omits critical context about prerequisites, side effects, validation, and return behavior.

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%, and the tool has nine parameters. The description mentions the file path and related item ids, but leaves title, id, description, agent_token, client_agent_id, claim_generation, and client_session_id unexplained.

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 resource: attaching a file path to the sprint. It is clear enough for an agent to understand the core action, but it does not explicitly distinguish this tool from sibling tools such as artifact_update or artifact_get.

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

Usage Guidelines2/5

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

The description gives no guidance about when to use artifact_add versus artifact_update, artifact_get, or artifact_list. The optional related-items note is parameter context, not usage guidance or exclusion criteria.

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