AgileToolHub
DocsUpdated August 19, 2026

AI Agent Tools for Agile and Scrum Workflows

Use AgileToolHub's free deterministic JSON tools from AI agents and developer workflows for story point estimation and sprint capacity planning.

AgileToolHub provides small, free JSON tools that AI agents and developer workflows can call without an account or API key. The endpoints are deterministic: the same valid input produces the same result, and no AI provider is required.

Use the AI-Friendly Agile Tools Directory to discover the available workflows, or open the OpenAPI specification for machine-readable definitions.

Available endpoints

EndpointUse it forMethod
/api/agent/story-pointEstimate one story from effort, complexity, uncertainty, risk, and dependenciesPOST
/api/agent/sprint-capacityCalculate maximum and recommended sprint capacity from team availabilityPOST
/api/agent/user-storyTurn feature notes into a Jira-ready story with acceptance criteriaPOST
/api/agent/acceptance-criteriaTurn a story into Gherkin and/or checklist criteriaPOST

For lightweight discovery, call /api/agent/tools. It returns the current tool names, endpoints, inputs, outputs, OpenAPI link, and documentation link.

Remote MCP

MCP-compatible clients can connect to https://agiletoolhub.com/mcp. The server exposes the same four tools through the standard Streamable HTTP transport and does not require an API key. Tool calls are stateless and return JSON inside MCP text content.

All responses are JSON. Send Content-Type: application/json. An invalid request returns a 400 response with an error field.

Story Point Estimator

Use this endpoint when an agent needs a quick, explainable first estimate before a human review.

curl -X POST https://agiletoolhub.com/api/agent/story-point \
  -H "Content-Type: application/json" \
  -d '{
    "story": "Add export filters",
    "factors": {
      "effort": 2,
      "complexity": 1,
      "uncertainty": 1,
      "risk": 0,
      "dependencies": 1
    }
  }'

Each factor accepts a value from 0 to 3. The response includes the Fibonacci estimate, confidence, score, high-scoring factors, and suggested follow-up actions.

The estimate is a preparation signal, not a replacement for the team's decision. For a shared estimate, send the story to Planning Poker and let the team vote independently.

Sprint Capacity Calculator

Use this endpoint to turn team availability and points-per-day assumptions into a planning range.

curl -X POST https://agiletoolhub.com/api/agent/sprint-capacity \
  -H "Content-Type: application/json" \
  -d '{
    "sprintDays": 10,
    "members": [
      { "name": "Developer 1", "daysAvailable": 8, "velocity": 2 },
      { "name": "Developer 2", "daysAvailable": 6, "velocity": 1.5 }
    ]
  }'

The response includes each member's capacity, the team's maximum capacity, and an 80% recommended capacity that leaves room for meetings, reviews, bugs, and unplanned work.

User Story Generator

Turn rough feature notes into a structured Markdown story that can be reviewed or pasted into Jira.

curl -X POST https://agiletoolhub.com/api/agent/user-story \
  -H "Content-Type: application/json" \
  -d '{"feature":"As a shopper, I want to save payment methods so checkout is faster","preset":"product"}'

The response includes the story, acceptance criteria, dependencies, clarifications, and a deterministic quality score. Optional fields are user, storyType (feature, improvement, or task), priority, and preset.

Acceptance Criteria Generator

Turn a story or feature note into testable Gherkin, checklist criteria, or both.

curl -X POST https://agiletoolhub.com/api/agent/acceptance-criteria \
  -H "Content-Type: application/json" \
  -d '{"story":"As a shopper, I want to save payment methods so checkout is faster","format":"gherkin"}'

The format can be gherkin, checklist, or both. Use the preset field to add Product, Engineering, API, or Tech Debt checks.

Recommended agent workflow

  1. Ask the agent to structure the story and identify unclear assumptions.
  2. Call the Story Point Estimator for a transparent first sizing signal.
  3. Share the story and open questions with the delivery team.
  4. Use Planning Poker for independent votes and discussion.
  5. Use the Sprint Capacity Calculator when comparing the agreed estimate with team availability.

Do not send passwords, API keys, customer information, private incident details, or other sensitive data. The team remains responsible for the product decision, estimate, and sprint commitment.

Try the Planning Poker

Use Planning Poker to generate cleaner, Jira-ready output in seconds.