Skip to main content
Glama
Sign In
bitmap-mcp

bitmap-mcp

Official
by BitmapAsset
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get an Ordinals inscription

get_inscription

Retrieve an Ordinals inscription's details by ID, including content type, owner, sat, genesis height, location, and content URL.

Instructions

Look up an Ordinals inscription by id and return its content type, owner address, sat, genesis height, current location, and content URL.

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": {
      "id": "<id>"
    },
    "name": "get_inscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInscription id, formatted as a 64-char txid followed by 'i' and an index, e.g. '6fb9...i0'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states the tool returns specific fields, indicating a read-only retrieval, but does not address error cases, authentication, or side effects. The 'look up' verb implies safety, though not explicitly.

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, compact sentence that lists the action and all relevant return values. No wasted words, and the information is front-loaded.

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 one-parameter lookup tool with no output schema, the description covers the purpose and return fields sufficiently. It lacks explicit differentiation guidance from sibling tools, but the resource-specific wording makes the tool's role clear within the family.

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 input schema fully documents the single 'id' parameter with format details. The description simply says 'by id' and adds no additional semantic meaning beyond the schema, so it stays at the baseline for high schema coverage.

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 uses the specific verb 'Look up' and clearly identifies the resource 'Ordinals inscription' by id, listing the returned fields (content type, owner address, sat, genesis height, current location, content URL). This distinguishes it from sibling tools like get_bitmap or get_fees.

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 description implies usage for looking up inscription details by id, but provides no explicit when-to-use or alternative references. It doesn't mention when not to use this tool or suggest other tools for different scenarios.

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