Tulina

oto_context

CALL THIS FIRST, before any other oto tool — it carries your org's working rules and guardrails. Returns the contextual instructions for your CURRENT effective scope: your org (its readme = its working rules; your role, active team and connectors, recent projects and runs) and YOU — your profile card (oto_profile) and your own readme (oto_guide scope=user delivery=init). No procedure index here: oto_procedure op=list. ⚠️ The same context is also injected at connection time, but do NOT assume you received it: several clients truncate it, and some drop it entirely. If you have not read it in this session, you are missing rules your org expects you to follow — including when an action needs human validation before it goes out. Platform-wide usage rules live in the notice guide — read it once per session too: oto_guide op=read slug=notice. Call it again after you switch org/team/project — or pass org=/project=/group= here: the toolbox and credentials follow the switch, this prose does not.

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_context"
  }
}

Input Schema

Name	Required	Description	Default
`_org`	No

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0

Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses that the same context is injected at connection time but that clients may truncate or drop it, that missing it means missing org rules including human-validation gates, and that credentials/toolbox follow an org switch while the prose context does not. These are non-obvious runtime behaviors, not restatements of the name.

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?

Front-loaded with the imperative directive, then the return contents, then caveats, so the reader gets the essential action in the first clause. It is longer than typical but nearly every sentence carries operational value; the mid-section warning is dense but justified given the truncation risk it describes.

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

Completeness5/5

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

There is no output schema, so the description enumerates what is returned (org readme, role, team, connectors, recent projects/runs, profile card, personal readme) and what is not (procedure index). Combined with the re-invocation trigger and the sessions-caveat, an agent has everything needed to call it correctly.

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 coverage is 0% for the single `_org` parameter, so the description must compensate. It does partially by saying 'pass org=/project=/group= here' and explaining the effect (toolbox and credentials follow the switch), but the schema only exposes `_org` as an integer, so the mentions of project/group do not map cleanly onto the documented input and are ambiguous about how to address them.

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 and resource ('returns the contextual instructions for your CURRENT effective scope') and enumerates the contents: org readme, role, team, connectors, projects, profile card, personal readme. It also explicitly distinguishes itself from siblings by noting there is no procedure index here (`oto_procedure op=list`) and pointing to the `notice` guide.

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?

Gives explicit ordering ('CALL THIS FIRST, before any other oto tool'), an explicit re-invocation condition (after switching org/team/project), and an explicit when-not/alternative split for the procedure index and the platform-wide notice guide. An agent knows exactly when to call this versus the other oto tools.

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?