Tulina

oto_use_group

Resolve a group (department) you belong to and get the RELIABLE way to act under it. NO session state (ADR 0038): pass group=<id> directly on each group-scoped call (its parent org is derived). Your default group is changed in the dashboard only. The group decides which group guide and shared secrets apply.

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": {
      "group_id": "<group_id>"
    },
    "name": "oto_use_group"
  }
}

Input Schema

Name	Required	Description	Default
`_org`	No
`group_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0

Behavior4/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 disclose real behavior: no session state is set, the parent org is derived automatically, and the default group can only be changed in the dashboard. It omits membership/permission requirements and what happens when the caller does not belong to the group.

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 key constraint (no session state, pass group id per call) is front-loaded and every sentence carries information. The all-caps 'RELIABLE' and 'NO session state' are slightly noisy but do emphasize the critical distinction.

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

Completeness3/5

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

For a 2-parameter, unannotated tool with no output schema, the description covers the important no-session-state semantics and what the group governs. It still leaves unclear what exactly is returned (guide content? secret references?) and what error surfaces if the group is invalid or inaccessible.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It explains `group=<id>` usage and clarifies that the parent org is derived, which implicitly covers the optional `_org` parameter, but it adds no detail on id format, lookup, or how `_org` may be overridden.

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?

States a concrete verb and resource: resolve a group (department) you belong to, and hints at the payoff ('the group decides which group guide and shared secrets apply'). It distinguishes itself from stateful siblings by declaring 'NO session state (ADR 0038)', though the phrase 'get the RELIABLE way to act under it' is vague about what is actually returned.

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 does give operational guidance: pass `group=<id>` directly on each group-scoped call, and note that the default group is changed only in the dashboard. However, it never explicitly says when to call this tool versus siblings like oto_use_org, oto_use_project, or oto_clear_group, leaving the agent to infer that this tool resolves rather than persists.

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?