Grandet

Relay terminology / 中转站术语

grandet_glossary

Read-onlyIdempotent

Look up the published Grandet relay glossary. Site labels are source claims and glossary terms explain them; they do not verify quality. Query q or category and follow pagination. Unknown terms include up to three related FAQ links.

Input Schema

Name	Required	Description	Default
`q`	No	Term or phrase to look up, e.g. "倍率" or "token group".
`host`	No	The assistant or app making this call, e.g. "claude-code" or "codex". Attribution only; it does not change results.
`lang`	No	Answer language: "en" or "zh-CN".	en
`page`	No	Result page, starting at 1.
`limit`	No	Results per page, 1–20.
`category`	No	Limit to one glossary category.
`targetApp`	No	Catalogue ID of the app that will use the API, e.g. "openclaw", "claude-code" or "codex". Selects compatible protocols and connection steps. Send it only when the user says where the API will be used.
`skillBuild`	No	Grandet Skill build ID when called from the Skill. Omit otherwise.
`skillVersion`	No	Grandet Skill version when called from the Skill, e.g. "0.3.0". Omit otherwise.

Output Schema

Name	Required	Description	Default
`faq`	No
`terms`	No
`schema`	No
`pagination`	No
`suggestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 18, 2026

addedInput schema / properties / host

Added value: +{
+  "description": "The assistant or app making this call, e.g. \"claude-code\" or \"codex\". Attribution only; it does not change results.",
+  "pattern": "^[a-zA-Z0-9._/-]{1,64}$",
+  "type": "string"
+}

addedInput schema / properties / skillBuild

Added value: +{
+  "description": "Grandet Skill build ID when called from the Skill. Omit otherwise.",
+  "maxLength": 256,
+  "type": "string"
+}

addedInput schema / properties / skillVersion

Added value: +{
+  "description": "Grandet Skill version when called from the Skill, e.g. \"0.3.0\". Omit otherwise.",
+  "maxLength": 32,
+  "type": "string"
+}

addedInput schema / properties / targetApp

Added value: +{
+  "description": "Catalogue ID of the app that will use the API, e.g. \"openclaw\", \"claude-code\" or \"codex\". Selects compatible protocols and connection steps. Send it only when the user says where the API will be used.",
+  "pattern": "^[a-zA-Z0-9._/-]{1,64}$",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "faq": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "maxItems": 3,
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "schema": {
+      "type": "string"
+    },
+    "suggestions": {
+      "items": {},
+      "type": "array"
+    },
+    "terms": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that glossary terms explain source claims but "do not verify quality," and that unknown terms return up to three related FAQ links. These are useful behavioral details not present in the schema or annotations. Auth, rate limits, and return format are not covered, but the output schema and annotations already handle much of that.

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 four short sentences and front-loads the core purpose. Every sentence adds useful information: purpose, epistemic caveat, query guidance, and unknown-term behavior. There is no redundant or filler content.

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

Completeness5/5

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

Given the 100% schema description coverage, the rich annotations, and the presence of an output schema, the description covers the remaining gaps well. It explains purpose, the non-verification caveat, pagination, and unknown-term behavior without needing to restate optional attribution parameters.

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 parameter semantics are already well documented. The description reinforces q/category and pagination but adds no syntax or format details beyond what the schema already provides. A baseline 3 is appropriate.

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 opens with a specific verb and resource: "Look up the published Grandet relay glossary." It also distinguishes the glossary from verification tools by explaining that terms explain site labels but "do not verify quality." This separates it from siblings such as grandet_quote_evidence or grandet_find_cheapest_api.

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 invocation context: "Query q or category and follow pagination." It also sets expectations for unknown terms, but it does not explicitly state when not to use the tool or name an alternative sibling. The purpose itself makes the appropriate use case clear.

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

All Grandet tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.