Skip to main content
Glama

Read a card

card_read
Read-onlyIdempotent

Returns one BrainVault v3 card: creator, official, tags, mint block, and its text only when public and the on-chain hash matches (sha256_ok). Private: text null; hidden: hidden true. Use verify_citations to check many refs at once. Read-only, free, no key. Unknown ref: error not_found.

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": {
      "ref": "<ref>"
    },
    "name": "card_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesBrainVault card ref, v3:N, e.g. v3:142

Output Schema

NameRequiredDescriptionDefault
refNo
textNo
blockNo
staleNo
hiddenNo
sourceNo
creatorNo
privateNo
sha256_okNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / ref / description
      Previous value: -"v3:N"New value: +"BrainVault card ref, v3:N, e.g. v3:142"
    • addedInput schema / properties / ref / pattern
      Added value: +"^v3:\\d{1,9}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "creator": {
      +      "type": "string"
      +    },
      +    "hidden": {
      +      "type": "boolean"
      +    },
      +    "private": {
      +      "type": "boolean"
      +    },
      +    "ref": {
      +      "type": "string"
      +    },
      +    "sha256_ok": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "text": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing conditional return behavior: text is only populated when the card is public AND the on-chain hash matches (sha256_ok), private cards yield text null, hidden cards yield hidden true, and unknown refs produce a not_found error rather than an empty result. It also states cost/auth posture ("Read-only, free, no key"), which the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: return contents first, then conditional visibility rules, then the batch alternative, then operational facts. The telegraphic fragments ("Private: text null; hidden: hidden true") are efficient but slightly clipped for easy scanning.

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?

Even though an output schema exists, the description explains the conditional semantics an agent needs to interpret it correctly (null text vs hidden flag vs not_found). With one well-documented parameter and no nested structures, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single ref parameter is fully described in the schema (pattern ^v3:\d{1,9}$, example v3:142), so the baseline is already high. The description adds failure semantics for an invalid or missing ref (error not_found) that the schema's pattern alone does not convey.

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?

States a specific verb and resource ("Returns one BrainVault v3 card") and enumerates the returned fields (creator, official, tags, mint block, text). It is unmistakably a single-card read, distinct from the batch sibling it names.

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?

Explicitly routes batch verification to verify_citations ("to check many refs at once"), which is real when-to-use-else guidance. It lacks an explicit when-not for this tool, but the single-vs-many split is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources