Hugging Bay

get_artifact_card

Read-only

Read an artifact model card, optionally as Markdown.

Input Schema

Name	Required	Description	Default
`id`	Yes
`markdown`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
Changed2 schema fields changedOct 26, 2026
- removedInput schema / properties / id / description
```
Removed value: -"Artifact or record id returned by a previous read."
```
- removedInput schema / properties / markdown / description
```
Removed value: -"markdown; true to enable, false to disable."
```

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / id / description

Added value: +"Artifact or record id returned by a previous read."

addedInput schema / properties / markdown / description

Added value: +"markdown; true to enable, false to disable."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that output can be Markdown; it says nothing about what a model card contains, whether missing artifacts error out, or what the Markdown flag changes in practice.

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?

One short sentence with zero filler, and the purpose is front-loaded. It is efficient, though its brevity comes at the cost of the missing details noted above.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But for a two-parameter tool with 0% schema description coverage and three closely related sibling artifact tools, the description omits required parameter semantics and sibling routing, leaving the agent under-informed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely fails to. It never explains whether 'id' is an artifact id, version id, or model-card id, nor what format 'id' expects, and 'markdown' is only loosely implied by 'optionally as Markdown'.

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?

States a clear verb and resource ('Read an artifact model card'), and specifically says 'model card' rather than a generic artifact, which hints at the distinction from get_artifact. However, it never names or contrasts with get_artifact, resolve_artifact, or search_artifacts, so sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

The only guidance is 'optionally as Markdown', which is a format choice rather than a when-to-use rule. There is no indication of when an agent should call this instead of get_artifact or resolve_artifact, and no exclusions or prerequisite context are given.

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

All Hugging Bay tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?