Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

sheets_create

Create a new empty Google spreadsheet. Returns {id, title, url, sheets}.

Name the tabs with sheets (in order): without it, Google creates ONE tab named in the account's locale (Sheet1, Feuille 1…), and a write to 'Prospects'!A1 right after fails because no such tab exists.

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": {
      "title": "<title>"
    },
    "name": "sheets_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
titleYesthe new spreadsheet's title.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
sheetsNothe tab titles to create, in order (e.g. ["Hypothèses", "P&L"]). Omitted = Google's single default tab.
_run_idNoOBLIGATOIRE à 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.
accountNoGoogle account (email) to act as — same choice as `_account`.
_accountNoCompte à OPÉRER quand plusieurs existent. `oto_identity(op='list')`.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/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 well: it discloses the return payload, states the spreadsheet is created empty, and warns that the default tab name is locale-dependent. It omits permission/scope requirements and where in Drive the file lands, which are the remaining gaps for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short blocks: purpose, return value, then parameter guidance. It is front-loaded and every sentence carries distinct information, with no filler.

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 nine-parameter creation tool with no annotations and no output schema, the description covers what the tool does, what it returns, and the one parameter whose misuse causes a real failure. Remaining omissions (auth/account selection behavior, destination folder) are partially covered by the schema's own descriptions.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema by explaining the consequence of omitting `sheets` (a locale-named single tab and a subsequent A1 write failure) rather than merely restating 'in order'. The oto meta-parameters are left entirely to the schema.

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 first sentence gives a specific verb and resource ('Create a new empty Google spreadsheet') plus the return shape, which is unambiguous. It does not explicitly distinguish itself from the sibling `sheets_spreadsheet`, though 'create a new empty' versus an existing-spreadsheet tool is a reasonably clear split.

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

Usage Guidelines4/5

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

The description clearly frames the situation where `sheets` should be supplied and explains the concrete downstream failure if it is omitted (a write to 'Prospects'!A1 fails). It stops short of naming when to prefer a sibling tool over creating a new spreadsheet, so there is no explicit alternative routing.

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