Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

oto_procedure_app

SHOW a process to the user: draws the procedure's process graph INLINE in the conversation (MCP App) — trigger, steps, checks and the connectors each step uses.

ALWAYS call it, FIRST, whenever the user asks about a process or procedure: to see it, understand it, explain it, review it, or after you create or change one. Then answer in text — the graph replaces no explanation. It gives YOU only the title: the steps are in oto_procedure op=get. If the process has no drawing yet, the answer tells you how to draw one: do it, then call this again.

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": {
      "slug": "<slug>"
    },
    "name": "oto_procedure_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
slugYesthe procedure's slug (cf. `oto_procedure op=list`).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.

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?

With no annotations, the description carries the full burden and does so: it discloses that output is a user-visible MCP App rendered inline, that the model itself receives only the title, and that step content must be fetched via oto_procedure op=get. It also discloses the failure path — if no drawing exists, the response explains how to create one and the tool must be called again.

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 action and its output medium, then the when-to-call rule, then the caveats. Slightly dense and the emphasis on 'ALWAYS ... FIRST' is repeated in spirit, but nearly every clause carries operational information.

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?

No output schema exists, and the description compensates by explaining exactly what the model receives back (only the title) versus what the user sees (the graph). The create-then-recall loop is fully spelled out, so an agent can invoke this correctly on the first try.

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 100%, with all three parameters documented in the schema, so the baseline applies. The description adds no meaning about the slug beyond implying it identifies the procedure, leaving the schema to do the work.

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 concrete verb and resource: it draws the procedure's process graph inline in the conversation, listing what the graph contains (trigger, steps, checks, connectors). It is clearly distinguished from the sibling oto_procedure, which is named as the source of the underlying step data.

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 rules: 'ALWAYS call it, FIRST, whenever the user asks about a process or procedure' with enumerated intents (see, understand, explain, review, after create/change), followed by the sequencing instruction to answer in text afterward. It also covers the fallback branch when no drawing exists yet.

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

All Tulina toolsInspect
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