Skip to main content
Glama

Traceable

by com.traceabledocs.app
OverviewDiscussionsAdmin

Set ID-grid cell

traceable_grid_cell
DestructiveIdempotent

Set one ID-grid cell's value, identified by the id-ROW (row.itemId or row.atOrder) and the 0-based colIdx. NON-DESTRUCTIVE: the cell keeps its identity and the row's trace links survive — setting the id column changes the visible TraceID without breaking links (unlike traceable_segment_write). id/text columns take the raw value, and a text column also takes an image as alt{width=60%} (upload it with traceable_image_upload); test-result normalises PASS/FAIL; checkbox normalises to true/false (true/yes/1/✓ vs false/no/0/✗); dropdown takes one of the column's options (matched ignoring case; any other value is refused). Link cells are NOT settable here — use traceable_link_create instead.

Input Schema

NameRequiredDescriptionDefault
rowYesIdentify the row by itemId or atOrder (pass one).
valueYesThe new cell value
colIdxYes0-based index of the column whose cell to set
documentIdYesThe document UUID
baseRevisionNoThe revision (meta.revision) from the traceable_doc_read, or the previous write, this change is based on. When given, the write is refused with nothing changed if the document has changed since, so you never overwrite edits you have not seen. Each write returns the current revision. The revision tracks the document's content rows, so changes that touch no row (its name and other metadata, the reference list, Test Plan entries) return it unchanged. A revision is an opaque value: compare it whole, never read meaning into its parts (they are not a counter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / baseRevision
      Added value: +{
+  "description": "The revision (meta.revision) from the traceable_doc_read, or the previous write, this change is based on. When given, the write is refused with nothing changed if the document has changed since, so you never overwrite edits you have not seen. Each write returns the current revision. The revision tracks the document's content rows, so changes that touch no row (its name and other metadata, the reference list, Test Plan entries) return it unchanged. A revision is an opaque value: compare it whole, never read meaning into its parts (they are not a counter).",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive/idempotent/not-read-only, yet the description adds substantial context beyond them: link/identity preservation, per-type value normalization (PASS/FAIL, checkbox true/false mappings, dropdown case-insensitive matching with refusal), image syntax, and link-cell non-settability. The prominent 'NON-DESTRUCTIVE' framing sits in tension with destructiveHint=true, though it is explicitly scoped to identity and trace-link survival rather than to the prior value being overwritten, so it does not logically contradict the annotation.

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?

A single dense paragraph that front-loads the core action before the qualifiers. It is information-dense with no filler, though the many inline normalisation clauses would scan better as a short list; still appropriately sized for the tool's complexity.

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 mutation tool with five parameters, a nested row object, and no output schema, the description covers purpose, alternatives, non-destructiveness, and value semantics. Return/revision behaviour is covered by the schema's baseRevision description, so little is missing; only the response shape is left implicit.

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 description coverage is 100%, so baseline is 3. The description goes beyond the schema by defining how `value` is interpreted per column type (raw text, image markup, PASS/FAIL normalisation, checkbox booleans, dropdown option matching) and by restating the itemId/atOrder row-identification contract, which materially aids correct invocation.

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 (Set), resource (one ID-grid cell's value), and scope (identified by id-ROW and 0-based colIdx). It is immediately distinguishable from siblings like traceable_segment_write, traceable_link_create, and traceable_image_upload, which it names explicitly.

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 when-not and alternatives: link cells are not settable here, use traceable_link_create; images are uploaded with traceable_image_upload; contrast with traceable_segment_write which breaks links. An agent knows exactly which sibling to pick under which condition.

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

All Traceable 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