Skip to main content
Glama
ExaDev

document-mcp

by ExaDev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

List .odb forms

odb_forms

List all forms declared in an .odb database, showing each form's data source and field-bound controls.

Instructions

Lists every form an .odb database declares, with each form's own data source and field-bound controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes.odb database to read. 'path' points at the .odb file on disk -- its extension is never used to infer a document format, since documents.js deliberately excludes 'odb' from DocumentFormat (an embedded database front end has no single natural target format -- tables, saved queries, and reports are three unrelated output shapes -- see that package's own README). 'bytesBase64' carries the .odb bytes inline; its 'format' field is required by the shared hybrid input shape but unused by every odb tool.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv2.1.8
    • changedInput schema / properties / source / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "path": {
-        "description": "Filesystem path to the document to read. The document format is inferred from the file extension.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "path"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "bytesBase64": {
-        "description": "Base64-encoded document bytes.",
-        "type": "string"
-      },
-      "format": {
-        "description": "The document format of bytesBase64 -- required, since inline bytes carry no filename to infer it from.",
-        "enum": [
-          "docx",
-          "pptx",
-          "xlsx",
-          "odt",
-          "odp",
-          "ods",
-          "odg",
-          "odf",
-          "markdown",
-          "pdf"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "bytesBase64",
-      "format"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "path": {
+        "description": "Filesystem path to the document to read. The document format is inferred from the file extension.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "bytesBase64": {
+        "description": "Base64-encoded document bytes.",
+        "type": "string"
+      },
+      "format": {
+        "description": "The document format of bytesBase64 -- required, since inline bytes carry no filename to infer it from.",
+        "enum": [
+          "docx",
+          "pptx",
+          "xlsx",
+          "odt",
+          "odp",
+          "ods",
+          "odg",
+          "svg",
+          "odf",
+          "csv",
+          "markdown",
+          "pdf"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "bytesBase64",
+      "format"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv1.1.6

TDQS

A3.8/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not state that the operation is read-only or non-destructive, nor does it mention any side effects, permissions, or output format. A simple listing operation is implied but not explicit.

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?

The description is a single, concise sentence that front-loads the purpose and key output details. It contains no wasted words and is easily parseable.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is adequate. It provides enough context to distinguish forms from other .odb entities and lets the schema handle parameter details. It does not explain return format, but for a listing tool this is often predictable.

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?

The tool description adds no parameter-specific details, but the input schema's description of 'source' is comprehensive (100% coverage), including why odb is excluded from document formats. Since the schema fully documents the parameter, the description's silence is acceptable, but no extra value is added.

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?

The description clearly states the tool lists all forms in an .odb database, with specifics about data sources and field-bound controls. This distinguishes it from sibling tools like odb_tables and odb_reports, which handle other entity types.

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 gives clear context that this tool is for forms in .odb databases, implicitly distinguishing it from siblings that target tables, reports, and queries. It does not explicitly state when not to use it, but the naming and context make usage unambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ExaDev/document-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server