Max size of open api yaml speficiation / Linked with the context?

GPT builders Plugins / Actions builders
,
1

Hi guys,

I’m currently developing several plugins, and I was wondering if the size of yaml file is limited in anyway and affecting the context size ?
I have several endpoints and these endpoints have sometime numero parameters as input.
I know that that each description is limited to 200 chars, but the whole file with the various properties can take a lit in terms of context.
I was wondering if it has any impact and if we should try to limit the length of it or not at all ?

Thanks in advance,

Anselme

2

Welcome to the forum.

My best guess is that the OpenAPI specification is used to create a similar Typescript file for the API e.g.

image

If the plugin installs with the manifest and OpenAPI specification validated than I would say all systems are go.

Manifest and OpenAPI specification (Click triangle to expand)

Manifest

{
  "schema_version": "v1",
  "name_for_human": "Erics evaluate",
  "name_for_model": "Erics_evaluate",
  "description_for_human": "Evaluate plugin.",
  "description_for_model": "Evaluate plugin.",
  "auth": {
    "type": "none"
  },
  "api": {
    "type": "openapi",
    "url": "http://localhost:5003/openapi.yaml",
    "is_user_authenticated": false
  },
  "logo_url": "http://localhost:5003/logo.png",
  "contact_email": "support@example.com",
  "legal_info_url": "https://example.com/legal"
}

OpenAPI specification

{
  "openapi": "3.0.1",
  "info": {
    "title": "Eric Evaluate",
    "description": "An pluin to evaluate to numbers and return a number.",
    "version": "v1"
  },
  "servers": [
    {
      "url": "http://localhost:5003"
    }
  ],
  "paths": {
    "/eval": {
      "post": {
        "operationId": "evaluate",
        "summary": "Evaluate two numbers and return a number.",
        "requestBody": {
          "required": true,
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "value1": {
                    "type": "number"
                  },
                  "value2": {
                    "type": "number"
                  }
                }
              }
            }
          }
        },
        "responses": {
          "200": {
            "description": "OK",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "properties": {
                    "value": {
                      "type": "number"
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}
3

Intuition says that the description has to be parsed by the AI, so making it too large will run into a token limit at some point.

4

it would be great to have more clarity on this, because it would help us optimize the way we are delivering data and optimizing data requests.

5

As I noted in another post, we signed up for ChatGPT plugin developer access knowing it was alpha. If Logan is spending time updating documentation then plugins will be delayed getting into the store, feedback to the teams working on the ChatGPT plugin interface will not happen, etc. Personally I can live with the hazards for now knowing this.

6

Don’t misjudge my comment: This is more a nice to have to understand and optimize efficiency.
Of course, I’m already happy to be able to develop plugins

1 Like