# No tool-level execution field from 2025-11-25

**Revision 2026-07-28 moved experimental tasks out of the core protocol into the io.modelcontextprotocol/tasks extension, so clients on the new revision ignore a tool’s 2025-11-25 "execution" field.**

Check `spec-execution-legacy` · MCP specification 2026-07-28 · default severity: advice · rubric 2.1.0. Last verified against MCP specification 2026-07-28: Key changes on 2026-11-18.

## What fails

The tool carries the 2025-11-25 "execution" field (task support). In 2026-07-28 tasks are an extension, so clients on the new revision ignore this field.

## The rule

> Move experimental tasks out of the core protocol and into an official extension (`io.modelcontextprotocol/tasks`).

Source: [MCP specification 2026-07-28: Key changes](https://modelcontextprotocol.io/specification/2026-07-28/changelog)

## How to fix it

Keep the field while you serve 2025-11-25 clients; for 2026-07-28 declare task support through the io.modelcontextprotocol/tasks extension.

1. Keep the execution field while you still serve 2025-11-25 clients.
2. For 2026-07-28 clients, declare task support through the io.modelcontextprotocol/tasks extension.
3. Upgrade the SDK; current versions handle both revisions.

### TypeScript SDK

```ts
import { McpServer } from '@modelcontextprotocol/server';
import * as z from 'zod';

const server = new McpServer({ name: 'issues', version: '1.0.0' });

server.registerTool(
  'export_report',
  {
    title: 'Export report',
    description: 'Start an export of one report and return a job ID. Use when the user asks for a downloadable report.',
    inputSchema: z.strictObject({
      report_id: z.string().describe('Report ID, for example REP-9'),
    }),
    annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: false },
  },
  async ({ report_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);
```

### Python SDK

```python
from typing import Annotated

from pydantic import Field
from mcp.server.mcpserver import MCPServer
from mcp.types import ToolAnnotations

server = MCPServer("issues")

@server.tool(
    title="Export report",
    annotations=ToolAnnotations(readOnlyHint=False, destructiveHint=False, openWorldHint=False),
)
def export_report(
    report_id: Annotated[str, Field(description="Report ID, for example REP-9")],
) -> str:
    """Start an export of one report and return a job ID. Use when the user asks for a downloadable report."""
    return "Done"
```

## Questions

### Is the execution field an error now?

No. It is ignored by 2026-07-28 clients, which is why the checker rates it as advice.

### What replaced it?

The official tasks extension, negotiated as an extension capability instead of a per-tool field.

## Related checks

- [The tools/list result carries resultType](https://isokron.ai/mcp-check/checks/spec-envelope-result-type)
- [_meta keys avoid prefixes reserved for MCP](https://isokron.ai/mcp-check/checks/spec-meta-reserved)
- [Tools that start jobs or queue work are not read-only](https://isokron.ai/mcp-check/checks/openai-readonly-starts-job)
- [MCP specification 2026-07-28: tools/list rules](https://isokron.ai/mcp-check/checks/protocol)

## Further reading

- [Shipping a production MCP server on the 2026-07-28 spec](https://isokron.ai/research/production-mcp-server)

Counts toward: MCP specification 2026-07-28.

Rubric: https://isokron.ai/mcp-check/rubric

Check your tool list: https://isokron.ai/mcp-check
