Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

artifact_list

Page through active sprint artifacts in compact newest-first rows to review recent work and paginate results by limit and offset.

Instructions

Page through active sprint artifacts as compact newest-first rows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "artifact_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
agent_tokenNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • 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"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 3,
+  "exclusiveMinimum": 0,
+  "maximum": 3,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Addedv0.1.17
  3. Removedv0.1.15
  4. First observedv0.1.9

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses newest-first ordering and compact rows, but says nothing about authentication, claim semantics, read-only behavior, or what happens with the agent_token/claim_generation parameters despite those implying a non-trivial access model.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. It efficiently conveys the listing action, scope, ordering, and row format.

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?

For a tool with six parameters including several authentication/claim-related fields and no output schema or annotations, one sentence is insufficient. An agent needs more detail on pagination limits, authentication expectations, and what 'compact rows' actually contain.

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 six parameters, so the description must compensate. 'Page through' weakly maps to limit/offset, but it does not explain the maximum limit of 3, defaults, or any of the four authentication/session parameters (agent_token, client_agent_id, claim_generation, client_session_id).

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 gives a specific verb ('page through') and resource ('active sprint artifacts'), plus useful scope details ('newest-first', 'compact rows'). It does not explicitly differentiate itself from siblings such as artifact_get or search, so an agent must infer that this is the list/pagination counterpart.

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?

The phrase 'page through' implies this tool is for retrieving multiple artifacts rather than one, but there is no explicit guidance on when to use it versus artifact_get, search, or other listing siblings. Usage is only implied by the scope ('active sprint artifacts').

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

Deploy Server

Other Tools