Skip to main content
Glama
Sign In

Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram

by ai.bowmark
OverviewDiscussionsAdmin

Jig cache

jig_cache
Idempotent

Used by an open jig to save a call's last good result. You do not need to call this.

Input Schema

NameRequiredDescriptionDefault
keyYesWhich call this result belongs to, as the page names it.
jigIdYesThe jig's id, as `jig_open` or `jig_list` returned it.
valueNoThe call's result, saved for the next time the page opens.

Output Schema

NameRequiredDescriptionDefault
okNoFalse on an error.
storedNoTrue when the result was saved.
messageNoWhy the call failed, when `ok` is false.
truncatedNoTrue when it was cut to fit the cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / jigId / description
      Added value: +"The jig's id, as `jig_open` or `jig_list` returned it."
    • addedInput schema / properties / key / description
      Added value: +"Which call this result belongs to, as the page names it."
    • addedInput schema / properties / value / description
      Added value: +"The call's result, saved for the next time the page opens."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "description": "Why the call failed, when `ok` is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "False on an error.",
+      "type": "boolean"
+    },
+    "stored": {
+      "description": "True when the result was saved.",
+      "type": "boolean"
+    },
+    "truncated": {
+      "description": "True when it was cut to fit the cache.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare write (readOnlyHint=false), idempotent and non-destructive; the description is consistent with them and adds the non-obvious context that this is an internal side-effect invoked by an open jig and that only the "last good" result is retained. It does not say what happens on repeated writes or whether a prior cached value is replaced, but the essential behavioral framing is present.

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?

Two short sentences, zero redundancy, and the most decision-relevant fact ("You do not need to call this") is present up front rather than buried. Nothing could be removed without losing information.

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 three-parameter internal write tool with full schema coverage and an output schema, the description supplies what an agent actually needs: that it is auto-invoked and that agent-side calls are unnecessary. Minor gaps (overwrite semantics, error behavior) are tolerable given the annotations and 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 description coverage is 100%, so the schema already explains key, jigId and value in detail. The description adds only marginal meaning (the value is a "last good result" saved for reopening the page), which is essentially a restatement of the schema's own parameter description. Baseline 3 applies when the schema does the heavy lifting.

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?

"Used by an open jig to save a call's last good result" names a concrete verb (save) and resource (a call's result) and ties it to the jig lifecycle, which separates it from siblings like jig_call or jig_get. It stops short of naming any single sibling it overlaps with, but the internal/auto-invoked framing makes its role distinguishable.

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?

"You do not need to call this" is an explicit when-not-to-use instruction, which is stronger than most definitions provide. It lacks a positive case (any condition under which an agent might legitimately call it), so it is not fully complete guidance.

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

All Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram 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