Skip to main content
Glama

Cards by creator

cards_by_creator
Read-onlyIdempotent

Returns cards one address minted, newest first, from the verified index: metadata only, never private text. Paging: pass the next_before you got back as before to get the next page (null = last page). Use card_read for a card's text. Read-only, free, no key; counts as 2 calls.

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": {
      "address": "<address>"
    },
    "name": "cards_by_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-100, default 50
beforeNoOnly cards with a card id below this number: the next_before from the previous page
addressYesThe minting Theta address, 0x + 40 hex

Output Schema

NameRequiredDescriptionDefault
blockNo
cardsNo
countNo
staleNo
sourceNo
addressNo
next_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"The minting Theta address, 0x + 40 hex"
    • addedInput schema / properties / address / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • changedInput schema / properties / before / description
      Previous value: -"Only cards with id below this (paging)"New value: +"Only cards with a card id below this number: the next_before from the previous page"
    • addedInput schema / properties / before / minimum
      Added value: +0
    • addedInput schema / properties / limit / default
      Added value: +50
    • addedInput schema / properties / limit / description
      Added value: +"1-100, default 50"
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "address": {
      +      "type": "string"
      +    },
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "cards": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "count": {
      +      "type": "integer"
      +    },
      +    "next_before": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses privacy behavior ('metadata only, never private text'), auth/cost ('free, no key'), and quota impact ('counts as 2 calls'), which materially affects planning. The paging contract with next_before is also spelled out.

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 tight sentences, front-loaded with what it returns, then paging, then the alternative tool. Every sentence carries distinct information with no filler.

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 an output schema exists, return values need no explanation; the description covers the remaining gaps an agent needs — privacy scope, paging loop, cost, auth, and the sibling alternative. Nothing required to call it correctly 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?

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining the before/next_before coupling with the previous response, which the schema alone does not convey. It does not restate limit bounds, but those are fully documented in the schema.

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 cards one address minted'), plus scope details (newest first, verified index, metadata only). It is immediately distinguishable from card_read, which the description explicitly routes text retrieval to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (card_read) and the condition that selects it ('for a card's text'), and gives explicit paging instructions for continuing past the first page. An agent knows both when to call this and how to iterate it without inference.

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