# Every required argument is declared

**Every name in "required" must also appear under "properties"; otherwise the model has no type or description for it, and with additionalProperties: false no valid call exists at all.**

Check `schema-required-unknown` · Schema and description quality · default severity: attention (or blocking, depending on the case) · rubric 2.1.0. Last verified against Anthropic: Writing effective tools for agents on 2026-11-18.

## What fails

A name listed in "required" is missing from "properties", so the model has no type or description for it. With "additionalProperties": false the tool cannot be called at all, which is blocking.

## The rule

> Avoid ambiguity by clearly describing (and enforcing with strict data models) expected inputs and outputs.

Source: [Anthropic: Writing effective tools for agents](https://www.anthropic.com/engineering/writing-tools-for-agents)

## How to fix it

Declare the argument under "properties", or remove it from "required".

1. Compare "required" with the keys of "properties" in each tool.
2. Declare the missing argument with a type and description, or remove it from "required".
3. Generate schemas from types so the two lists cannot drift.

### 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(
  'assign_issue',
  {
    title: 'Assign issue',
    description: 'Assign one issue to a person. Use when the user asks who should work on an issue.',
    inputSchema: z.strictObject({
      issue_id: z.string().describe('Issue ID, for example ISS-42'),
      assignee_id: z.string().describe('User ID of the new assignee'),
    }),
    annotations: { readOnlyHint: false, destructiveHint: true, openWorldHint: false },
  },
  async ({ issue_id, assignee_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="Assign issue",
    annotations=ToolAnnotations(readOnlyHint=False, destructiveHint=True, openWorldHint=False),
)
def assign_issue(
    issue_id: Annotated[str, Field(description="Issue ID, for example ISS-42")],
    assignee_id: Annotated[str, Field(description="User ID of the new assignee")],
) -> str:
    """Assign one issue to a person. Use when the user asks who should work on an issue."""
    return "Done"
```

## Questions

### How does this happen?

Usually after renaming an argument in "properties" and not in "required", or in schemas converted from another format.

### Why is it blocking with additionalProperties: false?

The required name must be present, but it is not a declared property, so additionalProperties: false forbids it. No argument object can satisfy both.

## Related checks

- [Unknown arguments are rejected](https://isokron.ai/mcp-check/checks/schema-additional-properties)
- [Every argument has a description](https://isokron.ai/mcp-check/checks/schema-param-description)
- [inputSchema and outputSchema are valid JSON Schema](https://isokron.ai/mcp-check/checks/spec-schema-valid)
- [MCP tool input and output schemas](https://isokron.ai/mcp-check/checks/schema)

Counts toward: Schema and description quality.

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

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