Workfile

Overview Schema Related Servers Score Discussions

Create a work card

project_card_create

Create a new work card with a concurrency-safe stable ID. Search first to mint a fresh record rather than reuse an existing one.

Instructions

Create one canonical Work card with a concurrency-safe stable ID. Search first: this mints a new record rather than finding an existing one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`due`	No	Target completion date, YYYY-MM-DD.
`area`	No	Part of the system this touches. Project-declared, so the accepted values vary; project_workspace reports them.
`axes`	No	Declared classification axes as { axis: value }, e.g. { context: "treasury" }. Project-declared, so the accepted values vary; project_workspace reports them.
`body`	No	Markdown body, written below the frontmatter.
`tags`	No	Free-form tags for filtering.
`type`	No	What kind of work this is.
`scope`	No	Repository paths this work will change. Declared here, enforced when the card is claimed.
`start`	No	Planned start date, YYYY-MM-DD.
`title`	Yes	What the card is about, in one line.
`effort`	No	Rough size: S, M or L.
`parent`	No	ID of the parent card. The hierarchy is bounded by cards.maxHierarchyDepth.
`source`	No	Where the work came from: an issue URL, a person, a meeting.
`status`	No	Starting lifecycle status.	backlog
`depends`	No	IDs of cards that must close first. Blocks this card from being ranked as actionable.
`related`	No	IDs of records worth reading alongside this one.
`priority`	No	How urgent the work is.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`record`	Yes	A canonical record with its body, revision and reference graph.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed22 schema fields changedv0.5.4Aug 3, 2026

addedInput schema / properties / area / description

Added value: +"Part of the system this touches. Project-declared, so the accepted values vary; project_workspace reports them."

addedInput schema / properties / axes / description

Added value: +"Declared classification axes as { axis: value }, e.g. { context: \"treasury\" }. Project-declared, so the accepted values vary; project_workspace reports them."

addedInput schema / properties / body / description

Added value: +"Markdown body, written below the frontmatter."

addedInput schema / properties / depends / description

Added value: +"IDs of cards that must close first. Blocks this card from being ranked as actionable."

addedInput schema / properties / due / description

Added value: +"Target completion date, YYYY-MM-DD."

addedInput schema / properties / effort / description
```
Added value: +"Rough size: S, M or L."
```
addedInput schema / properties / effort / enum
```
Added value: +[
+  "S",
+  "M",
+  "L"
+]
```

addedInput schema / properties / parent / description

Added value: +"ID of the parent card. The hierarchy is bounded by cards.maxHierarchyDepth."

addedInput schema / properties / priority / description
```
Added value: +"How urgent the work is."
```

addedInput schema / properties / priority / enum

Added value: +[
+  "critical",
+  "high",
+  "medium",
+  "low"
+]

addedInput schema / properties / related / description

Added value: +"IDs of records worth reading alongside this one."

addedInput schema / properties / scope / description

Added value: +"Repository paths this work will change. Declared here, enforced when the card is claimed."

addedInput schema / properties / source / description

Added value: +"Where the work came from: an issue URL, a person, a meeting."

addedInput schema / properties / start / description
```
Added value: +"Planned start date, YYYY-MM-DD."
```
addedInput schema / properties / status / default
```
Added value: +"backlog"
```
addedInput schema / properties / status / description
```
Added value: +"Starting lifecycle status."
```

addedInput schema / properties / status / enum

Added value: +[
+  "backlog",
+  "next",
+  "doing",
+  "review",
+  "blocked",
+  "deferred",
+  "done",
+  "discarded"
+]

addedInput schema / properties / tags / description
```
Added value: +"Free-form tags for filtering."
```

addedInput schema / properties / title / description

Added value: +"What the card is about, in one line."

addedInput schema / properties / type / description
```
Added value: +"What kind of work this is."
```

addedInput schema / properties / type / enum

Added value: +[
+  "epic",
+  "idea",
+  "feature",
+  "bug",
+  "task",
+  "audit",
+  "docs",
+  "chore"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "record": {
+      "additionalProperties": true,
+      "description": "A canonical record with its body, revision and reference graph.",
+      "properties": {
+        "archived": {
+          "description": "Whether the record lives in the archive directory.",
+          "type": "boolean"
+        },
+        "body": {
+          "description": "Markdown body below the frontmatter.",
+          "type": "string"
+        },
+        "created": {
+          "description": "Creation date, YYYY-MM-DD.",
+          "type": "string"
+        },
+        "file": {
+          "description": "File name within the collection directory.",
+          "type": "string"
+        },
+        "id": {
+          "description": "Stable record ID.",
+          "type": "string"
+        },
+        "incoming": {
+          "description": "Backlinks: references other records make to this one.",
+          "items": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "incomingTotal": {
+          "description": "Total backlinks, which may exceed the returned page.",
+          "type": "integer"
+        },
+        "issues": {
+          "description": "Validation findings doctor would report for this record.",
+          "items": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "kind": {
+          "description": "Record family: card, doc, change, release or memory.",
+          "type": "string"
+        },
+        "outgoing": {
+          "description": "References this record makes to others.",
+          "items": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "path": {
+          "description": "Repository-relative path to the Markdown file.",
+          "type": "string"
+        },
+        "recordType": {
+          "description": "Type within the family.",
+          "type": "string"
+        },
+        "revision": {
+          "description": "Content hash to pass back as expectedRevision on the next write.",
+          "type": "string"
+        },
+        "status": {
+          "description": "Lifecycle status.",
+          "type": "string"
+        },
+        "tags": {
+          "description": "Free-form tags.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "title": {
+          "description": "Human-readable title.",
+          "type": "string"
+        },
+        "updated": {
+          "description": "Date of the last write, YYYY-MM-DD.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "record"
+  ],
+  "type": "object"
+}

First observedv0.1.0Aug 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false (it mutates), which the description's 'Create' and 'mints a new record' wording confirms—no contradiction. The description adds the concurrency-safe stable ID behavior as useful context. However, as a creation tool with an output schema, it doesn't disclose return behavior or whether partial failures occur, and 100% schema coverage means the description carries moderate additional burden beyond annotations.

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 two concise sentences with no filler. The operational guidance ('search first') is front-loaded and adds value. It could arguably mention the distinction from project_card_write explicitly, but the existing structure is tight and purposeful.

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

Completeness4/5

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

Given a complex 16-parameter tool with an output schema and annotations present, the description covers the key operational concern (search-first to avoid duplicates, concurrency-safe ID). The nuanced project-declared values (area, axes) are delegated to project_workspace which is correctly referenced. It's reasonably complete for a create operation, though could note what the canonical-creation invariant ensures about duplicates.

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 description coverage is 100%, so the schema documents all 16 parameters thoroughly. The description doesn't add parameter-level meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting, though the description's comment about project_workspace for accepted area/axes values aligns with what schema already notes.

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 clear verb+resource ('Create one canonical Work card') with a distinctive attribute ('concurrency-safe stable ID'). It distinguishes from project_card_write (which shares the 'create' domain) by emphasizing 'one canonical' card with concurrency safety. However, it doesn't explicitly name the sibling it differs from, leaving some differentiation implicit.

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?

The phrase 'Search first: this mints a new record rather than finding an existing one' provides explicit usage guidance, implying the agent should check for existing cards (via project_next or project_search) before calling create to avoid duplication. This gives clear context on when this tool is appropriate. It doesn't explicitly list excluded sibling tools, but the guidance is actionable.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/illodev/workfile'

If you have feedback or need assistance with the MCP directory API, please join our Discord server