Tulina

oto_admin_set_option

[super admin] Set (on=true) or remove (on=false) a NON-billed option flag on a user or org (e.g. option='beta', 'claude_subscription'). Read by access.has_option. entity_type='user'|'org', entity_id=sub|org_id. A key of the entitlements catalogue ('unipile', 'platform_unmetered', 'unipile_seats', 'members_max', 'platform_key:') is REFUSED with 409 billing_moved: those are declared rights, set by the billing service (oto-commerce) only — offering one happens there, not here. For a platform-mode connector this ALSO grants/revokes its platform key (so the option is actually usable, not a dead has_option without a key); the platform_key field reports what happened (granted / no_platform_key / byo_inert / revoked); a connector whose grant requires a quota is refused with grant_quota_required (grant its key with daily_quota instead). An option can also GATE tools (e.g. 'beta'), and a tool list is computed at handshake: visible_next_session: true means the change lands on a session other than yours and shows up when its owner reconnects — false means your own tool list was just refreshed. Neither is a failure. expires_at bounds the gift ('YYYY-MM-DD' = end of that day UTC, so the date itself is still covered; ISO timestamp also accepted). OMITTED leaves any existing deadline UNTOUCHED — re-granting never silently clears one; empty string makes the gift open-ended. Past the deadline the option stops being granted, the row stays, and clearing the date reopens it. Refused with 409 partner_org_out_of_scope on an org hosted by a third-party tenant: its owners are that partner's customers, not ours.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "option": "<option>",
      "on": "<on>"
    },
    "name": "oto_admin_set_option"
  }
}

Input Schema

Name	Required	Description	Default
`on`	Yes
`_org`	No
`option`	Yes
`entity_id`	Yes
`expires_at`	No
`entity_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses the platform-key side effect for platform-mode connectors, the platform_key result field values, the grant_quota_required refusal and its workaround, tool gating recomputed at handshake with visible_next_session semantics, and expires_at lifecycle (omitted = untouched, empty = open-ended, past deadline = row retained).

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

Conciseness4/5

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

The core action is front-loaded in the first sentence, followed by exclusions and side effects in a sensible order; nearly every clause carries operational meaning. It is dense and parenthetical-heavy, which costs some scanability, but little is genuinely redundant.

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 mutation tool with no annotations and no output schema, the definition covers refusals, side effects, return field semantics, and deadline behavior thoroughly. The only completeness gap is the undocumented `_org` parameter and the absence of any statement about auth prerequisites beyond the [super admin] tag.

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 coverage is 0%, so the description must compensate and largely does: it defines 'on', entity_type values, entity_id (sub|org_id), the option key space, and the full expires_at format and edge-case semantics. The remaining gap is `_org`, a nullable integer parameter never mentioned, leaving its purpose to inference.

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?

States a specific verb pair (set on=true / remove on=false), the exact resource (a non-billed option flag), the target scope (user or org), and the audience ([super admin]). It also pre-empts the closest look-alike operation by declaring that billed entitlement keys are refused.

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

Usage Guidelines5/5

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

Explicit routing: entitlement-catalogue keys ('unipile', 'unipile_seats', 'platform_key:<connector>', etc.) are refused with 409 billing_moved because granting there belongs to the billing service, and partner-hosted orgs are refused with partner_org_out_of_scope. The agent is told both when this tool is the right call and which cases belong elsewhere.

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

All Tulina tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?