PAT-0150 - Interface Mismatch

Primary Lenses

• LEN-0200 - Interface Contract Lens

  Compares declared interface structure to observed runtime structure to detect contract deviations.

Secondary Lenses

• LEN-0230 - Normalization Lens

  Transforms structurally equivalent variants into a canonical form to prevent false divergence.

Primary Issue Matches

• Tool Call Contract Mismatch

  The AI or agent calls a tool with names, arguments, types, modes, or shapes that do not match the declared tool interface.

Supporting Issue Matches

• Agent Cannot Choose Tool Without Tool Result

  The agent needs a tool result to choose the right tool, but cannot obtain that result without choosing a tool first.

• Agent Gets Conflicting Tool Authority

  An agent receives conflicting authority signals about whether, when, or how it may use a tool, connector, function, or integration.

• AI Output Breaks Parser

  The AI output causes a parser, validator, importer, or structured-output consumer to fail.

• Citation Points to Wrong Source

  A citation, reference, link, or source pointer is present, but it points to the wrong source, wrong passage, wrong document, or unsupported evidence.

• Invalid JSON Output

  The AI returns malformed JSON or structured output that cannot be parsed.

• Model and Workflow Disagree on Next Step

  The AI model recommends or selects a next step that conflicts with the workflow state, required handoff, routing rule, or process sequence.

• Nested Fields Do Not Match

  The AI returns nested structured fields whose internal shape, hierarchy, parent-child relationship, or contained values do not match the expected structure.

• Output Breaks the Next Step

  The AI output looks acceptable by itself but cannot be used by the next tool, workflow step, parser, reviewer, or downstream consumer.

• Prompt Changed but Workflow Did Not

  A prompt changes but the workflow, parser, review step, routing rule, or downstream expectation still assumes the old prompt behavior.

• Same Contract Name Has Different Meanings

  The same prompt, schema, field, policy, tool, or workflow contract name is used in different places with different meanings.

• Tool Can Act Without Responsible Authority

  A tool, connector, function, or integration can perform an action without a declared responsible authority for that action.

• Tool Exists but Required Inputs Are Missing

  A usable tool or integration exists, but the AI or agent does not have the required inputs, permissions, fields, identifiers, or context needed to call it correctly.

• Tool Result Not Integrated Correctly

  The AI receives a tool result but misreads, ignores, overwrites, misplaces, or fails to incorporate it correctly into the final output or workflow state.

• Tool Rules and Prompt Rules Conflict

  Tool, connector, function, or MCP rules conflict with prompt instructions, causing the AI or agent to face incompatible requirements.

• Wrong Field Types

  The AI returns fields with values whose types do not match the expected schema, such as strings where numbers, booleans, arrays, objects, or enums are required.

Ontology Metadata

Code

PAT-0150

Version

[email protected]

Ontology release

0.1.0

Updated

2026-05-10T00:00:00Z

History

• 0.1.0 — 2026-05-10T00:00:00Z — Created

  Promoted reviewed Pattern ontology entry: Interface Mismatch.

  Receipt impact: None

View full ontology changelog