Skip to main content
Glama

Read a hub card

hub_get

Read a published Verdict card by hub:owner/slug or versioned ref to inspect its question, answers, threshold, licence, lineage, agreement numbers, versions, and public cases.

Instructions

Read a published card: its question and answers, threshold, licence, lineage, author-reported agreement numbers, versions and some public cases. ref is hub:owner/slug or hub:owner/slug@rv_….

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": "hub_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubNo
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does useful work by disclosing the payload shape, including the hedged "some public cases" that warns the case list is partial and that only public cases are returned. It says nothing about failure behavior for unknown/private refs, permission requirements, or response size/pagination.

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?

Two sentences with no filler: the return contents are front-loaded and the identifier format follows. The enumerated content list is dense but each item earns its place by telling the agent what it can rely on getting back.

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

Completeness3/5

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

For a read-only tool with no annotations and no output schema, listing the returned fields is the right compensation and largely sufficient for an agent to decide to call it. It still leaves open the `hub` parameter's role and any error/empty-result semantics, which matter given a 2-parameter schema with zero description coverage.

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 0%, and the description meaningfully documents the one parameter that matters, `ref`, including its hub:owner/slug and hub:owner/slug@rv_… forms. However, the second parameter `hub` (uri format) is never mentioned, and the description leaves ambiguous whether `hub` is needed in addition to the already owner-qualified `ref`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ("Read") plus a specific resource ("a published card") followed by an enumeration of what is returned (question and answers, threshold, licence, lineage, agreement numbers, versions, public cases). That makes the tool's function unmistakable and clearly separates it from hub_search/fork_rubric-style siblings, though no sibling is named explicitly.

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?

Usage is only implied: the presence of a required `ref` in hub:owner/slug form signals this is the fetch-by-reference path, as opposed to discovery. It never states when to prefer this over hub_search or what to do if the caller only knows a name, and gives no preconditions (e.g., whether the card must be published and public).

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