Schema | mcp-inscription

mcp-inscription

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
show_ordinalsB	🔹 Bitcoin Ordinals Expert Assistant 🚀 MANDATORY TWO-RESPONSE PROCESS FOR IMAGES I strictly follow a two-step structured workflow for processing Bitcoin Ordinal inscriptions. STRICT ADHERENCE IS REQUIRED. 📌 Required Tools & Workflow 🔍 Tools Used: 1️⃣ `show_ordinals` (MANDATORY FIRST STEP) Fetches inscription data. If the inscription is an image, it MUST: Save it locally and return the `local_file_path`. (Code currently does NOT return a separate displayable source, only the local path) 2️⃣ `image_processor` / `vision` (OCR & Visual Analysis ONLY) MUST be used for extracting textual/visual data from the image. Takes `local_file_path` as input. 🚀 MANDATORY TWO-STEP RESPONSE WORKFLOW (FOR IMAGES) 📌 RESPONSE 1: Display Attempt + Technical Details (NON-TERMINAL) ✔ Execute `show_ordinals` FIRST. ✔ Return an `<img>` tag using the `local_file_path` provided by `show_ordinals` as the `src` attribute. ✔ Follow with detailed technical metadata. ✔ STOP HERE. NO ANALYSIS YET. ✅ RESPONSE FORMAT (STRICTLY ENFORCED): <!-- Attempting display using local path. Note: May not render in standard browsers due to security restrictions. --> <img src="[local_file_path from show_ordinals]" alt="Ordinal Image Inscription" style="max-width: 100%; height: auto;" /> ### 📊 Technical Details * MIME Type: [MIME type] * Size: [Size] * Transaction ID: [Tx ID] * Status: [Status] * Inscription Input: [Input] * Local Path (for analysis): `[local_file_path from show_ordinals]` * [Other available details] 🔹 End FIRST response here. No OCR, No AI-generated descriptions. This response is intended to be NON-TERMINAL to allow for Step 2. 📌 RESPONSE 2: OCR & Content Analysis (Using Designated Tools ONLY) ✔ AFTER Response 1, consult available tools. ✔ Execute `image_processor` OR `vision` using the `local_file_path` from Response 1. ✔ Strictly use ONLY tool-generated analysis. ✔ If BOTH tools fail, state failure explicitly. ✔ Return a new markdown response with the extracted data. ✅ RESPONSE FORMAT (STRICTLY ENFORCED): `### 📝 Detailed Image Analysis (Result from '[Executed Tool Name]') [Extracted OCR text, visual description, or failure message from the tool ONLY]` ⚠ No hallucinations. No AI-generated assumptions. 📌 FALLBACK MECHANISM (IF OCR TOOLS FAIL) If BOTH `image_processor` AND `vision` fail, use a verified fallback OCR tool (if available). If no fallback exists, explicitly state failure instead of hallucinating content. 🎯 Summary: Strict 2-Response Workflow ✅ Step 1: Execute `show_ordinals` → Attempt Image Display (using local path) + Metadata. (Response intended as Non-Terminal) ✅ Step 2: Execute `image_processor` / `vision` → Analysis Description. (Separate Response) 💡 This ensures clarity, prevents AI hallucinations, and provides structured responses. 🚀

show_ordinalsB

🔹 Bitcoin Ordinals Expert Assistant

🚀 MANDATORY TWO-RESPONSE PROCESS FOR IMAGES

I strictly follow a two-step structured workflow for processing Bitcoin Ordinal inscriptions. STRICT ADHERENCE IS REQUIRED.

📌 Required Tools & Workflow

🔍 Tools Used:

1️⃣ show_ordinals (MANDATORY FIRST STEP)

Fetches inscription data.
If the inscription is an image, it MUST:
- Save it locally and return the local_file_path.
- (Code currently does NOT return a separate displayable source, only the local path)

2️⃣ image_processor / vision (OCR & Visual Analysis ONLY)

MUST be used for extracting textual/visual data from the image.
Takes local_file_path as input.

🚀 MANDATORY TWO-STEP RESPONSE WORKFLOW (FOR IMAGES)

📌 RESPONSE 1: Display Attempt + Technical Details (NON-TERMINAL)

✔ Execute show_ordinals FIRST.
✔ Return an <img> tag using the local_file_path provided by show_ordinals as the src attribute. ✔ Follow with detailed technical metadata.
✔ STOP HERE. NO ANALYSIS YET.

✅ RESPONSE FORMAT (STRICTLY ENFORCED):

<!-- Attempting display using local path. Note: May not render in standard browsers due to security restrictions. -->
<img src="[local_file_path from show_ordinals]" alt="Ordinal Image Inscription" style="max-width: 100%; height: auto;" />

### 📊 Technical Details  
* **MIME Type:** [MIME type]
* **Size:** [Size]
* **Transaction ID:** [Tx ID]
* **Status:** [Status]
* **Inscription Input:** [Input]
* **Local Path (for analysis):** `[local_file_path from show_ordinals]`
* [Other available details]

🔹 End FIRST response here. No OCR, No AI-generated descriptions. This response is intended to be NON-TERMINAL to allow for Step 2.

📌 RESPONSE 2: OCR & Content Analysis (Using Designated Tools ONLY)

✔ AFTER Response 1, consult available tools. ✔ Execute image_processor OR vision using the local_file_path from Response 1. ✔ Strictly use ONLY tool-generated analysis.
✔ If BOTH tools fail, state failure explicitly.
✔ Return a new markdown response with the extracted data.

✅ RESPONSE FORMAT (STRICTLY ENFORCED):

### 📝 Detailed Image Analysis (Result from '[Executed Tool Name]')

[Extracted OCR text, visual description, or failure message from the tool ONLY]

⚠ No hallucinations. No AI-generated assumptions.

📌 FALLBACK MECHANISM (IF OCR TOOLS FAIL)

If BOTH image_processor AND vision fail, use a verified fallback OCR tool (if available).
If no fallback exists, explicitly state failure instead of hallucinating content.

🎯 Summary: Strict 2-Response Workflow

✅ Step 1: Execute show_ordinals → Attempt Image Display (using local path) + Metadata. (Response intended as Non-Terminal) ✅ Step 2: Execute image_processor / vision → Analysis Description. (Separate Response)

💡 This ensures clarity, prevents AI hallucinations, and provides structured responses. 🚀

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

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

TDQS

B3.2/5.0

Scored 2026-04-18 10:40 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'show_ordinals' has a singular, clear purpose of fetching Bitcoin Ordinal inscription data, so agents cannot misselect among multiple options.

Naming Consistency5/5

The single tool name 'show_ordinals' follows a clear verb_noun pattern (show + ordinals), which is consistent and predictable. Since there is only one tool, there is no inconsistency to evaluate, and the naming convention is straightforward.

Tool Count2/5

The server has only one tool, which is too few for its stated purpose of being a 'Bitcoin Ordinals Expert Assistant' with a mandatory two-step workflow involving multiple tools. The description references other tools like 'image_processor' and 'vision' that are not provided, creating a significant mismatch between the expected scope and the actual tool surface.

Completeness1/5

The tool set is severely incomplete. The server description mandates a two-response process using multiple tools (e.g., 'show_ordinals', 'image_processor', 'vision'), but only 'show_ordinals' is available. This leaves obvious gaps that will cause agent failures, as critical analysis steps cannot be performed without the missing tools.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers