Ginbing

Start a trademark draft

create_filing_draft

Idempotent

Start a new trademark application draft in the connected Ginbing account. Reuse the same creationKey when retrying; the existing draft is returned. The customer completes and submits the application on the Ginbing website.

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": {
      "creationKey": "<creationKey>"
    },
    "name": "create_filing_draft"
  }
}

Input Schema

Name	Required	Description	Default
`creationKey`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "draft": {
-        "additionalProperties": false,
-        "properties": {
-          "accountUrl": {
-            "format": "uri",
-            "type": "string"
-          },
-          "draftRevision": {
-            "maximum": 9007199254740991,
-            "minimum": 0,
-            "type": "integer"
-          },
-          "id": {
-            "exclusiveMinimum": 0,
-            "maximum": 9007199254740991,
-            "type": "integer"
-          },
-          "registrationType": {
-            "anyOf": [
-              {
-                "enum": [
-                  "word-mark",
-                  "figurative-mark"
-                ],
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "status": {
-            "enum": [
-              "draft",
-              "pending_payment",
-              "paid",
-              "in_review",
-              "filed",
-              "completed",
-              "cancelled"
-            ],
-            "type": "string"
-          },
-          "trademarkName": {
-            "type": "string"
-          },
-          "updatedAt": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "status",
-          "draftRevision",
-          "trademarkName",
-          "registrationType",
-          "updatedAt",
-          "accountUrl"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "draft"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "code": {
-        "maxLength": 128,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "code"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "draft": {
+        "additionalProperties": false,
+        "properties": {
+          "accountUrl": {
+            "format": "uri",
+            "type": "string"
+          },
+          "draftRevision": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          "id": {
+            "exclusiveMinimum": 0,
+            "maximum": 9007199254740991,
+            "type": "integer"
+          },
+          "registrationType": {
+            "anyOf": [
+              {
+                "enum": [
+                  "word-mark",
+                  "figurative-mark"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "status": {
+            "enum": [
+              "draft",
+              "pending_payment",
+              "paid",
+              "in_review",
+              "completed",
+              "cancelled"
+            ],
+            "type": "string"
+          },
+          "trademarkName": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "status",
+          "draftRevision",
+          "trademarkName",
+          "registrationType",
+          "updatedAt",
+          "accountUrl"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "draft"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "code"
+    ],
+    "type": "object"
+  }
+]

First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=false, and destructiveHint=false. The description adds real value beyond that by explaining the idempotency mechanism (same creationKey returns the existing draft) and by scoping the tool's responsibility: it only starts the draft, and the customer finishes and submits on the Ginbing website. It does not mention auth requirements, draft lifetime, or failure behaviour.

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?

Three short sentences, each carrying distinct information: purpose, retry semantics, and handoff to the website. The purpose is front-loaded and nothing is redundant or padding.

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 single-parameter creation tool with annotations covering the safety/idempotency profile and an output schema covering return values, the description is nearly complete: it explains what is created, how retries behave, and where submission happens. Minor gaps remain around authentication and draft lifecycle, but nothing an agent needs in order to invoke it correctly is missing.

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 0%, so the schema documents only type and length for creationKey, not its meaning. The description partially compensates by explaining that the key drives idempotent retries, which is the crucial semantic. It still leaves the key's expected format, uniqueness scope, and how to generate one unaddressed.

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 ('Start a new trademark application draft') plus the target account ('connected Ginbing account'), which is enough to distinguish it from get_filing_draft, list_filing_drafts, and update_filing_draft. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

The retry guidance ('Reuse the same creationKey when retrying') tells the agent how to behave on a repeat call, and the final sentence clarifies that submission happens on the Ginbing website, not here. However, there is no explicit when-to-use versus the sibling update_filing_draft or get_filing_draft, and no exclusion saying this tool cannot submit or modify an existing draft.

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

All Ginbing tools Inspect

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

Need Help?