Saga MCP

by spranab

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

tracker_init

Idempotent

Initialize a project tracker. Creates a new project if none exists, or retrieves existing project details.

Instructions

Initialize the tracker for a project. If the database is empty, creates a project with the given name. If a project already exists, returns its info.

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": "tracker_init"
  }
}

Input Schema

Name	Required	Description	Default
`project_name`	No	Name for a new project (only used if DB is empty)
`project_description`	No	Description for the new project

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.3Mar 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations (idempotentHint=true) are supported by description's conditional logic. Description adds context beyond annotations: explains that creation only happens if DB is empty, and existing projects return info. No contradictions.

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?

Two sentences efficiently convey purpose, conditional behavior, and parameter usage. No redundancy, front-loaded information.

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

Completeness5/5

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

Given simple parameters, no output schema, and good annotations, the description covers both scenarios comprehensively. No missing information for an agent to decide or invoke correctly.

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% with clear parameter descriptions. Description restates that project_name is only used if DB empty, but adds no new semantics beyond schema. Adequate but no extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool initializes a tracker for a project, with explicit conditional behavior: creates if DB empty, returns info if exists. Distinguishes from siblings like project_create and project_get by handling initialization logic.

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?

Provides clear context on when to use (initializing a tracker). Does not explicitly exclude alternative tools, but the conditional behavior makes usage clear. Among siblings, it's distinct from tracker_dashboard, etc.

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