Get one public project template by numeric id, including its ordered task list (title, description, status/priority defaults, offset and duration in days).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Template id. |
| Name | Required | Description | Default |
|---|---|---|---|
| template | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / template / properties / tasks / items / properties / duration_days / anyOfAdded value: +[
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / template / properties / tasks / items / properties / duration_days / maximumRemoved value: -9007199254740991Output schema / properties / template / properties / tasks / items / properties / duration_days / minimumRemoved value: --9007199254740991Output schema / properties / template / properties / tasks / items / properties / duration_days / typeRemoved value: -"integer"Output schema / properties / template / properties / tasks / items / properties / offset_days / anyOfAdded value: +[
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / template / properties / tasks / items / properties / offset_days / maximumRemoved value: -9007199254740991Output schema / properties / template / properties / tasks / items / properties / offset_days / minimumRemoved value: --9007199254740991Output schema / properties / template / properties / tasks / items / properties / offset_days / typeRemoved value: -"integer"Output schema / properties / template / properties / tasks / items / properties / priority_basisAdded value: +{
+ "anyOf": [
+ {
+ "enum": [
+ "source_recorded",
+ "operational_default",
+ "operator"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+}Output schema / properties / template / properties / tasks / items / requiredPrevious value: -[
- "order_index",
- "title",
- "description",
- "default_status",
- "default_priority",
- "offset_days",
- "duration_days"
-]New value: +[
+ "order_index",
+ "title",
+ "description",
+ "default_status",
+ "default_priority",
+ "priority_basis",
+ "offset_days",
+ "duration_days"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "template": {
+ "additionalProperties": false,
+ "properties": {
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "type": "integer"
+ },
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "source_guide": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "task_count": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "tasks": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "default_priority": {
+ "type": "string"
+ },
+ "default_status": {
+ "type": "string"
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "duration_days": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "offset_days": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "order_index": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "order_index",
+ "title",
+ "description",
+ "default_status",
+ "default_priority",
+ "offset_days",
+ "duration_days"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "slug",
+ "name",
+ "description",
+ "source_guide",
+ "task_count",
+ "url",
+ "tasks"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "template"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds useful behavioral scope beyond that: it commits to the 'public' template space and describes the shape of the returned content (ordered tasks with defaults and offsets), which tells the agent what a successful call yields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence, front-loaded with the action and identifier and then the payload, with no filler. Every clause carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value documentation is not strictly required, and the description's brief return summary is a bonus. For such a simple read tool the coverage is close to complete, with only failure behavior for a nonexistent or non-public id left unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single 'id' parameter is fully documented ('Template id.', exclusiveMinimum 0). The description only reinforces the type with 'numeric id', adding little beyond the schema, which matches the baseline for fully covered parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get one public project template by numeric id') and adds the scope qualifier 'public' plus the returned content. The singular 'one' plus the id-keyed lookup clearly separates it from the sibling kanbai_list_templates, so an agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: fetch this when you already hold a template id, rather than when enumerating templates. However, the description never explicitly contrasts itself with kanbai_list_templates or states what to do when the id is unknown, so the guidance remains inferential.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.