Skip to main content
Glama

models

Get model metadata

get_model_card
Read-only

Public metadata card for one model: title, category, tags, formats, preview, canonical URL, license note. Same payload as GET /x402/card/{hash}.json.

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": {
      "model_id": "<model_id>"
    },
    "name": "get_model_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes8-char hex model id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's added value is in disclosing that the data is public (no auth required) and mirroring a REST endpoint ('Same payload as GET /x402/card/{hash}.json'), which lets an agent predict the response shape. It stops short of covering not-found behavior or caching/rate limits.

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?

Two compact sentences: the first front-loads purpose and return fields, the second adds an equivalence hint. No filler or redundancy.

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?

With one fully described parameter and no output schema, the field enumeration does the necessary work of telling the agent what to expect back. Missing only edge-case behavior (unknown id, whether 'license note' is full text or a summary).

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 coverage is 100% with a regex pattern and '8-char hex model id' already documented, so the baseline of 3 applies. The endpoint reference '{hash}' loosely reinforces that model_id is a hash, but no additional format or source guidance is given.

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?

The description names a specific resource ('Public metadata card for one model') and enumerates the payload fields, so the agent knows exactly what comes back. It does not explicitly contrast with download_model or search_models, but the metadata-only framing makes the distinction inferable.

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 implied rather than stated: fetch this when you already have a model_id and want metadata rather than the file itself. There is no explicit 'use this instead of X when Y' guidance and no mention of what to do when the id is unknown.

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