Oi

Create Context

oi.contexts.create

Create an Oi Context in the current organization. By default this creates a private draft; publish: true releases the initial version and publishes it publicly. Use this only when the user explicitly asks to create or import a Context and has confirmed the source license permits reuse. Prefer markdown content in content; use privateContent for organization-private instructions that should not be published.

Plan and Billing

Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Context name.
`slug`	No	Optional organization-unique slug using lowercase letters, numbers, and hyphens.
`tags`	No	Optional tags.
`skills`	No	Optional skill identifiers.
`content`	No	Markdown Context content.
`enabled`	No	Whether the Context is enabled.
`license`	No	Optional plaintext license or reuse terms for this Context.
`publish`	No	Whether to release the initial draft as version 1 and publish it publicly after creation. Use only when the source license permits publication.
`release`	No	Whether to release the initial draft as version 1 after creation.
`categories`	No	Optional category labels.
`sourceSlug`	No	Optional source repository or public Context slug for provenance.
`syncEnabled`	No	Whether future source sync should be enabled.
`privateContent`	No	Optional private markdown instructions for this organization.
`shortDescription`	No	Optional short summary.
`sourceOrganizationSlug`	No	Optional source owner slug for provenance.
`suggestedFollowUpsEnabled`	No	Whether clients may suggest follow-up prompts.
`allowRuntimeInstructionUpdates`	No	Whether runtime feedback may update private instructions.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavioral detail beyond the annotations: creation defaults to a private draft, `publish: true` releases and publishes publicly, and `privateContent` is for organization-private instructions. The annotations already indicate a write operation, and the description does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded and well structured, but the 'Plan and Billing' section is generic boilerplate that adds length and distracts from the tool-specific guidance. It is organized, but not every sentence earns its place in a tool definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 17 parameters, the description provides the essential creation lifecycle context, licensing conditions, and private/public distinction. Since an output schema exists, return-value documentation is not required, and the description covers the main decisions an agent needs to make when calling this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds extra value by distinguishing `content` as markdown body versus `privateContent` as non-published private instructions, and by explaining the `publish` parameter's effect on the initial draft.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create an Oi Context in the current organization.' It further clarifies the default behavior (private draft) and the publish option, which distinguishes this creation action from sibling tools like update, get, or use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool 'only when the user explicitly asks to create or import a Context' and requires confirmation that the source license permits reuse. This gives strong when-to-use guidance, though it does not explicitly name alternative sibling tools for comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Oi tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation4/5

Resource prefixes (contexts, skills, guardrails, workflows, connections) make most tools clearly distinct, and parallel lifecycle verbs are scoped by resource name. The main ambiguity is within the guardrails publish/release/unpublish lifecycle and between brain.save-feedback, contexts.save-draft-feedback, and the two report tools, though detailed descriptions mostly resolve it.

Naming Consistency4/5

Tools overwhelmingly follow an oi.<resource>.<verb> snake_case pattern, with create/get/list/update/use repeated consistently across resource types. Deviations include resource-less oi.recommend, noun-style oi.auth.whoami, and inconsistent release handling (separate guardrails.release vs action=release on contexts/skills update).

Tool Count2/5

38 tools is too many for a single server, mainly because the same lifecycle pattern is repeated across Contexts, Skills, Guardrails, and Workflows. Each tool may be individually justifiable, but the set feels bloated and could benefit from consolidation or splitting into per-resource servers.

Completeness3/5

CRUD coverage is uneven: Guardrails have create/update/delete/list/get plus publish/unpublish/release, while Contexts, Skills, and Workflows lack any delete or archive tool, and Brain has only save-feedback with no read/update/delete path. Connections and auth are read/use-only, which may be intentional but leaves management actions absent.

Create Context

Plan and Billing

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources