Skip to main content
Glama
Sign In
xuzhougeng

ScientificFigureLibrary

by xuzhougeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plan a direct-intake Working Revision

figure_library_plan_working_revision
Read-onlyIdempotent

Validate user-confirmed figure image and code intake, then return an immutable Working Revision plan without calling a model or executing code.

Instructions

Validate user-confirmed image/code intake and return an immutable Working Revision plan. The operations never calls a model or executes code.

Input Schema

NameRequiredDescriptionDefault
modeNo
tagsNo
titleNo
intakeNo
licenseNo
runtimeNo
titleEnNo
languageNo
packagesNo
assetKindNo
assessmentNo
codeAssetsNo
codeStatusNo
plotFamilyNo
provenanceNo
templateIdNo
applicationNoFigureYa-style biological use cases as Markdown; required for new or updated Working revisions. Not visual encodings.
dataProfileNo
descriptionNo
visualAssetsNo
confirmationsNo
visualProfileNo
evidenceAssetsNo
agentAssessmentNo
executionStatusNo
figureCodeLinksNo
referenceAssetsNo
validationStateNo
scientificQuestionNo
canonicalCodeAssetIdNo
primaryVisualAssetIdNo
primaryPreviewOverrideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.2
    • addedInput schema / properties / titleEn
      Added value: +{
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed6 schema fields changedv0.6.8
    • addedInput schema / properties / application
      Added value: +{
+  "description": "FigureYa-style biological use cases as Markdown; required for new or updated Working revisions. Not visual encodings.",
+  "maxLength": 8000,
+  "type": "string"
+}
    • addedInput schema / properties / codeAssets / items / properties / rights
      Added value: +{
+  "properties": {
+    "attribution": {
+      "maxLength": 4000,
+      "type": "string"
+    },
+    "distribution": {
+      "enum": [
+        "local_only",
+        "public"
+      ],
+      "type": "string"
+    },
+    "license": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "license",
+    "distribution"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / evidenceAssets / items / properties / rights
      Added value: +{
+  "properties": {
+    "attribution": {
+      "maxLength": 4000,
+      "type": "string"
+    },
+    "distribution": {
+      "enum": [
+        "local_only",
+        "public"
+      ],
+      "type": "string"
+    },
+    "license": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "license",
+    "distribution"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / referenceAssets / items / properties / rights
      Added value: +{
+  "properties": {
+    "attribution": {
+      "maxLength": 4000,
+      "type": "string"
+    },
+    "distribution": {
+      "enum": [
+        "local_only",
+        "public"
+      ],
+      "type": "string"
+    },
+    "license": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "license",
+    "distribution"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / runtime
      Added value: +{
+  "properties": {
+    "dependencies": {
+      "items": {
+        "properties": {
+          "assetPath": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "codePath": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "codePath",
+          "assetPath"
+        ],
+        "type": "object"
+      },
+      "maxItems": 100,
+      "type": "array"
+    },
+    "entrypoint": {
+      "maxLength": 1000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "inputs": {
+      "items": {
+        "properties": {
+          "assetPath": {
+            "maxLength": 1000,
+            "minLength": 1,
+            "type": "string"
+          },
+          "codePath": {
+            "maxLength": 1000,
+            "minLength": 1,
+            "type": "string"
+          },
+          "required": {
+            "const": true,
+            "type": "boolean"
+          },
+          "role": {
+            "enum": [
+              "example_data",
+              "source_data",
+              "private_reference"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "codePath",
+          "assetPath",
+          "required",
+          "role"
+        ],
+        "type": "object"
+      },
+      "maxItems": 1000,
+      "type": "array"
+    },
+    "output": {
+      "properties": {
+        "mediaType": {
+          "const": "image/png",
+          "type": "string"
+        },
+        "previewPath": {
+          "maxLength": 1000,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "previewPath",
+        "mediaType"
+      ],
+      "type": "object"
+    },
+    "schema": {
+      "const": "figure-library.runtime-closure.v1",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema",
+    "entrypoint",
+    "inputs",
+    "output"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / visualAssets / items / properties / rights
      Added value: +{
+  "properties": {
+    "attribution": {
+      "maxLength": 4000,
+      "type": "string"
+    },
+    "distribution": {
+      "enum": [
+        "local_only",
+        "public"
+      ],
+      "type": "string"
+    },
+    "license": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "license",
+    "distribution"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / scientificQuestion
      Added value: +{
+  "maxLength": 2000,
+  "type": "string"
+}
  4. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotent and non-destructive, so the safety bar is lower. The description nonetheless adds real value by stating the operation never calls a model or executes code and that the plan is immutable — exactly the properties an agent needs to trust the result given the runtime/executionStatus parameters.

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 tight sentences with the core fact (validate, then return an immutable plan) front-loaded, and the no-model/no-execution guarantee placed immediately after. Nothing is wasted, though the brevity contributes to the parameter gap.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 32-parameter, deeply nested planning tool with no output schema, two sentences are far from enough. The description conveys the key behavioral guarantee but leaves the entire confirmation/validation structure and the expected return of the plan unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 32 parameters at 3% schema description coverage, the description must carry the burden, yet it explains only 'image/code intake' and 'user-confirmed'. Complex inputs such as confirmations, validationState, figureCodeLinks, runtime closure and assessment are undocumented in both schema and description.

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 description states a specific verb+resource: validate user-confirmed image/code intake and return an immutable Working Revision plan. An agent can tell it is a plan-only operation. It does not explicitly name the apply_working_revision sibling that consumes the result, but the 'plan' semantics are clear.

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

Usage Guidelines2/5

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

There is no when/when-not guidance, no mention that the output should be handed to figure_library_apply_working_revision, and no statement of prerequisites beyond 'user-confirmed'. The agent must infer the plan-then-apply workflow from the tool name alone.

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

Deploy Server

Other Tools