Glossary
additionalProperties
A JSON Schema keyword that, set to false, rejects any field the schema does not declare. OneLifeVibe tool schemas set it to false.
Updated November 12, 2026
- Standard
- JSON Schema
At OneLifeVibe
- Each OneLifeVibe tool publishes its inputSchema in tools/list (connectors) and GET /api/platform/v1/tools (Platform API). Schemas set additionalProperties: false.
What it means
additionalProperties is a JSON Schema keyword for object schemas. It controls what happens when an instance contains a field name that the schema does not list under properties. Set it to false and any such field makes the object fail validation. Set it to true, or leave it out, and extra fields are allowed. The keyword is about field names at one object level, not about values or types.
Use it when a payload should match a fixed contract. A tool that expects two named arguments can set additionalProperties to false so a third, undeclared argument does not pass silently. That keeps callers from guessing field names or adding metadata the receiver never agreed to handle.
How it works
A validator walks the object members. For each member name, it checks the properties keyword. Names found there are validated against their own schemas. Names not found there fall to additionalProperties. With false, the validator reports the extra name as a schema violation. With a schema value instead of false, the extra values would be validated against that schema. With true or no keyword, they pass.
The check applies per object. If a declared property is itself an object with its own schema, that nested schema can also set additionalProperties. Read each level. Setting false at the top does not by itself describe nested fields, and a nested object can have its own rule. Stick to the field names and nesting the published schema declares.
How OneLifeVibe uses it
Each OneLifeVibe tool publishes its inputSchema. For connectors, the schema comes back in tools/list. For the Platform API, it is published at GET /api/platform/v1/tools. The inputSchema for each tool sets additionalProperties to false.
That means the arguments you send should use only the fields declared in that tool's inputSchema. If you add an undeclared field, even one that looks harmless, schema validation rejects the request. Before you build a call, read the inputSchema for that specific tool and match its property names and nesting. If a call fails this way, compare your arguments with the schema and remove the fields it does not declare.
Common mistakes
The usual mistake is treating extra fields as harmless. With additionalProperties set to false, they are not ignored. Another is copying arguments from one tool to another because the names look similar. Each tool has its own inputSchema, so use the one for the tool you are calling.
Watch nested objects. A field can be declared at the top level and still have a nested schema that rejects undeclared members. Also check spelling and case: only the exact property names in the schema are declared. Do not add your own tracking or session fields to tool arguments unless the schema declares them.
Questions
What does additionalProperties: false do in a tool inputSchema?
It makes schema validation reject any argument name that the inputSchema does not declare. OneLifeVibe tool schemas set it to false, so send only the declared fields. If you add an extra key, the request fails schema validation.
Where do I find the inputSchema for a OneLifeVibe tool?
Connectors get it from tools/list, and the Platform API publishes it at GET /api/platform/v1/tools. Read the schema for the exact tool you plan to call before you send arguments. It lists the property names that are allowed.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.