TeamShared

work_close

Mark a work item done or cancelled. Result includes org + bound.

If the item's playbook sets artifact_required, closing done is refused (handoff_required) until the item has an attached artifact or a comment with a pointer (file:<id>, drive:<id>, a PR URL).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent`	No	Override agent identity
`work_id`	Yes	Work item UUID
`work_status`	No	done or cancelled	done

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "anyOf": [
-      {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedAug 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious behavior: the artifact/handoff gate and the refusal code, plus a note that the result carries org and bound. Missing is permission/auth requirements and whether the transition is reversible.

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?

Front-loads the core action in one sentence, then the gating rule in a short second paragraph. The mention of ``org`` + ``bound`` in the result is slightly redundant given an output schema exists, but nothing else is wasted.

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?

Covers the key state-transition precondition and relies appropriately on the output schema for return values. What is left implicit is the relationship to work_update and the identity semantics of the optional agent override.

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%, so work_id, work_status and agent are already documented in the schema. The description confirms only the two terminal statuses and adds no format or interaction detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource (mark a work item done/cancelled) and names the two terminal statuses. However, it does not distinguish itself from the sibling work_update, which plausibly also changes status, so the agent must infer the boundary.

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?

It gives one concrete precondition (closing 'done' is refused with handoff_required when the playbook sets artifact_required), which is useful context. But there is no explicit when-to-use-this vs work_update guidance or statement about when cancellation is appropriate.

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

All TeamShared tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.