Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

data_row_comments

Read the comments people left on ONE datastore row, oldest first within a page; before_id (= the previous next_before_id) reads older ones. Comments are not row values: they never change the row or its history.

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": {
      "datastore": "<datastore>",
      "row_id": "<row_id>"
    },
    "name": "data_row_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNo
limitNoComments per page, the most recent page first (200 at most).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
row_idYes
_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.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
before_idNoRead the next (older) page: the previous answer's `next_before_id`.
datastoreYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose real behavior: deterministic ordering, page-scoped traversal, and that reading comments never mutates the row or its history. It stops short of permission requirements or what happens for a missing row/invalid cursor.

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?

Two sentences, front-loaded with the core action, and the pagination mechanic is stated compactly. Dense but no filler; the semicolon clause does real work rather than restating the name.

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?

There is no output schema, yet the description never sketches what a comment looks like (author, timestamp, body) beyond referencing `next_before_id`, and it does not say how the agent knows pagination has ended. Adequate for calling, thin for interpreting results of an 8-parameter tool.

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?

Coverage is 63%, and the description adds meaning the schema does not: it ties `before_id` to the previous response's `next_before_id`, which is a cross-call contract no single schema field states. The remaining infra params (_org, _group, _project, _run_id) are only explained by 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?

States a specific verb and resource: 'Read the comments people left on ONE datastore row', with the exclusivity of 'ONE' and a note that comments are not row values. It implicitly contrasts with the singular data_row_comment sibling by framing this as a read, but it never names that sibling, so differentiation requires an inference.

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?

Pagination guidance is explicit — fetch with no `before_id` for the newest page, then feed the previous `next_before_id` back in to walk older. Usage relative to alternatives is only implied: nothing says when to use this instead of data_row_history or data_row_comment, so the agent must infer.

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