MCP, Tools & Integrations

Primary Issues

• 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.

• 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.

• 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 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.

• Too Many Tool Calls

  The AI or agent makes more tool calls, searches, retrievals, API calls, or integration actions than the task requires or permits.

Also Related Issues

• AI Output Breaks Parser

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

• 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.

• 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 Rules and Prompt Rules Conflict

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

• 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.

Ontology Metadata

Code

CAT-0040

Version

[email protected]

Ontology release

0.1.0

Updated

2026-05-10T00:00:00Z

History

No public history entries recorded.

View full ontology changelog