Tulina

http

Read-only

Read the org's custom connectors (Custom API) — ops: list, setup_link. Calls, import and changes: http_act.

list (default): without _account, every custom connector of the org (tools connected once for every member: account, label, description, action names) — start here. With _account: that connector's definition, its actions with their input schema. Call an action with http_act(op="call", operation=…, args={…}).
setup_link: a link to connect a tool that has no dedicated connector (a payroll, ERP or any SaaS with an API key) → {url, prefilled, instructions}. Send the url to the person who holds the key; they paste the key in the form, never in the chat — this tool takes no secret. If a key was already pasted in a chat, tell them to revoke it and create a new one.

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": "http"
  }
}

Input Schema

Name	Required	Description	Default
`op`	No	list (default) \| setup_link.	list
`_org`	No	Org (id) de CET APPEL. `oto_list_orgs()`.
`label`	No	setup_link — name of the tool to connect (e.g. "Acme Payroll").
`_group`	No	Équipe (id) de CET APPEL, sous son org parente.
`_run_id`	No	OBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
`_account`	No	Compte à OPÉRER parmi : `Cal.com` (org), `Qonto` (org). `oto_identity(op='list')`.
`_project`	No	Projet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
`base_url`	No	setup_link — API root to pre-fill (e.g. https://api.acme.test/v1), no query.
`doc_path`	No	setup_link — path of the API's OpenAPI JSON, relative to base_url.
`_instance`	No	Instance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
`auth_mode`	No	setup_link — bearer \| header \| query \| basic \| oauth2 \| none.
`header_name`	No	setup_link — header NAME carrying the key, header mode (e.g. x-api-key).
`query_param`	No	setup_link — parameter NAME carrying the key, query mode.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantive behavior beyond that — the return shape of `setup_link` (`{url, prefilled, instructions}`), the fact that the tool never takes a secret, where the key must be pasted, and what to do with an already-leaked key (revoke and recreate). It stops short of describing result volume or limits for the org-wide `list`, which keeps it from a 5.

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 verb, resource and op list, then two scannable bullets that map one-to-one onto the enum values. Slightly verbose in the parenthetical tool enumeration ('account, label, description, action names'), but every sentence carries operational content.

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 13-parameter, no-required-field tool with no output schema, the description covers both ops, the branch condition, the return shape of `setup_link`, and the security workflow. The gap is the call-context/identity parameters, which are left entirely to the schema.

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 100%, so the baseline is 3 and the schema already documents all 13 fields, including the setup_link parameters. The description adds genuine meaning for `_account` (absent = summary of every connector; present = full definition plus action input schemas), but says nothing about the call-context parameters (`_org`, `_group`, `_project`, `_run_id`).

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 ('Read the org's custom connectors (Custom API)') and immediately enumerates the two ops it supports. It also explicitly hands off 'Calls, import and changes' to `http_act`, so the agent can tell it apart from the similarly named `http_act`, `http_get` and `http_post` siblings without opening a schema.

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 an explicit entry point ('`list` (default) ... start here'), names the alternative tool for the excluded cases (`http_act` for calls/import/changes), and distinguishes the two modes of `list` by presence or absence of `_account`. It even prescribes the follow-up call pattern with `http_act(op="call", ...)`.

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?