Skip to main content
Glama
Sign In

Liro

by dev.liro
OverviewDiscussionsAdmin

Get a Liro component's code

get_component_code
Read-onlyIdempotent

The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Liro account's token; Pro components need the caller's Liro lifetime access. Install with the shadcn CLI instead when you can run commands (see get_installation).

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

Input Schema

NameRequiredDescriptionDefault
slugYesA component slug, like "data-table".
include_dependenciesNoAlso return every file it imports (the theme, foundations, sibling components). Default true. Set false only if those are already in the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description's added burden is lighter and it still goes further by disclosing the authorization model per component tier. 'Ready to save at the paths given' also tells the agent the payload is path-keyed file content rather than prose. This is behavioral context the annotations cannot convey.

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 with no filler: what you get first, then the access requirement, then the alternative path. Every clause carries information an agent needs before calling.

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 no output schema, the description does the necessary work of signaling that the return is file-path-keyed source. Auth requirements are fully spelled out. It could still say more about volume or how large multi-file responses behave, but nothing essential is missing for a two-parameter read.

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% and both parameters, including include_dependencies with its default and the advice to set it false when files already exist, are documented in the schema itself. The description only restates 'every file it imports', adding no syntax or format detail beyond that baseline.

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 the complete source for one component plus every file it imports, formatted so it can be saved at the given paths. That is clearly distinct from get_installation, which is named. It never names get_component, the likely metadata sibling, so the differentiation from that tool 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 Guidelines4/5

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

Gives an explicit routing rule: use the shadcn CLI via get_installation when you can run commands. It also states the access precondition per tier (free token vs Pro lifetime access). It stops short of saying when to prefer get_component instead of this source dump.

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

All Liro toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources