Skip to main content
Glama

Install a Foundry44 component

get_component

Steps to add a Foundry44 component to the user's project, for any stack (plain HTML, React with or without shadcn, other), with its markup, options and pitfalls. Follow them in the user's project. Pro components need the user's Pro key in this server's Authorization header. Getting a Pro component counts as a download and ends the buyer's 14-day refund window: call get_component only for the Pro component the user chose, never to compare.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe component's name, as search_components gives it (e.g. 'spotlight-card').
settingsNoOptional values that differ from the defaults: an option by its name (e.g. {"duration": 800}); a colour by its CSS variable (e.g. {"--f44-spotlight-card-color": "secondary"}) with a palette role of the project (brand, secondary, text, background, muted) or a #rrggbb hex.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses an auth requirement (Pro key in the server's Authorization header) and an irreversible side effect (the call counts as a download and ends the buyer's 14-day refund window). It also warns that getting a Pro component is effectively a purchase, which is exactly the kind of consequence an agent must know before invoking.

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?

Purpose is front-loaded, then prerequisites, then the refund warning, which is a sensible ordering. It is dense but every sentence carries information; the phrase 'Follow them in the user's project' is slightly awkward since the steps are the tool's return value, not something the description produces.

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?

For a two-parameter tool with no annotations and no output schema, the description covers the essential unknowns: purpose, auth, irreversible cost, and the single-use constraint. What remains unaddressed is minor but real: whether free components need the Pro header, and what a failure (missing or invalid key) looks like.

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%, so the schema already explains 'name' (as given by search_components) and 'settings' with examples of option names, CSS-variable colours and palette roles. The description adds only the constraint that 'name' should be the single component the user chose, which is useful but minimal; baseline 3 is appropriate.

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 specific verb and resource: it returns steps to add a Foundry44 component to the user's project, including markup, options and pitfalls, across any stack. It implicitly distinguishes itself from search_components ('call get_component only for the Pro component the user chose, never to compare'), though the title 'Install a Foundry44 component' is slightly misleading since the tool returns instructions rather than installing.

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?

Explicitly names the alternative workflow ('never to compare' implies search_components is for comparison) and the condition that selects this tool: only after the user has chosen one specific component. It also states a hard prerequisite, the user's Pro key in the Authorization header, that an agent would otherwise miss.

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