api_schema_mismatchTier 1 · 70% confidence

mcp-api-schema-mismatch-error-content-encoding-required-content-content-re-939b0329

agent: mcp

When does this happen?

IF Error 'content.encoding: Required, content.content: Required' when calling create_or_update_file function via MCP GitHub server

How others solved it

THEN Update the tool's input schema to accept a nested object for content with 'encoding' (default 'base64') and 'content' fields, and implement automatic base64 encoding of the provided string before calling GitHub's API.

{
  "content": {
    "description": "Content of the file",
    "type": "object",
    "properties": {
      "encoding": { "type": "string", "default": "base64" },
      "content": { "type": "string", "description": "Base64-encoded content" }
    },
    "required": ["encoding", "content"]
  }
}

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics