Tulina

oto_admin_connector_setting

Connector properties that the DATABASE may override, per platform or per org — the registry constant is only the default. op=list / set (connector, key, value; org_id omitted = platform-wide) / clear / reload. Keys: cardinality (mono|multi): how many accounts one entity may hold for that connector; platform.ops on forager, platform-wide: what the shared key serves, comma-separated tool:op or tool (default forager_person:phone_numbers, read at each call); the same key on elevenlabs (default elevenlabs_act:create_speech). ⚠️ Overrides are held in MEMORY, so a row takes effect only after reload — and reload is PER-PROCESS: reloading preprod does not reload prod.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oto_admin_connector_setting"
  }
}

Input Schema

Name	Required	Default
`op`	No	list
`key`	No	cardinality
`_org`	No
`value`	No
`org_id`	No
`connector`	No

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and discloses the critical behavior that overrides live in MEMORY, take effect only after reload, and reload is per-process. It still omits auth requirements, whether clear affects only memory or the database, and what list returns.

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 text is dense but front-loaded: purpose first, then operation modes, key semantics, and finally the reload warning. The platform.ops detail is long but operationally necessary; overall it is efficient though somewhat difficult to scan.

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 complex admin configuration tool with no annotations, no output schema, and 0% schema coverage, the description covers purpose, operation modes, scope, key values, defaults, and the memory/reload caveat. Missing permission requirements and list/clear effects or return shape keep it short of full completeness.

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?

Despite 0% schema description coverage, the description adds substantial meaning: it names op choices, links set to connector/key/value, states org_id omission behavior, and explains cardinality and platform.ops semantics with defaults. The `_org` parameter is never explained, and parameter requirements for clear/reload/list are only partially specified.

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

Purpose4/5

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

The description states a specific resource (connector override properties) and named operations (list/set/clear/reload), with per-platform/per-org scope. It is clear what the tool administers, but it does not explicitly distinguish itself from nearby admin/config siblings such as oto_admin_set_option or oto_connector.

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

Usage Guidelines3/5

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

It explains how to use each operation and that omitting org_id scopes the setting platform-wide, including defaults and reload behavior. However, it gives no explicit when-to-use versus alternatives, no when-not guidance, and no prerequisites such as required admin permissions.

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?