Skip to main content
Glama

Get the documented props (API) of an AI Canvas component

get_component_props
Read-onlyIdempotent

Returns a component's prop table with each prop's type, required status, default, and purpose so you can check configuration options before writing JSX or answering what can be customized.

Instructions

Return the prop table of one component: every prop with its type, whether it is required, its default and what it does. Free, needs no account, and far smaller than the full source. Call it before writing JSX for a component you have not read, or to answer "what can I configure on X". A component with no table takes no props: it is self-contained and adapted by editing its source.

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_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRegistry slug from a search or list result, e.g. "andromeda-button-system", "filter-menu".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), yet the description adds real value: it is free, needs no account, and is much smaller than the source. Most importantly it discloses the zero-prop edge case — a component with no table takes no props and is adapted by editing its source — which an agent could not infer from annotations or schema.

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?

Four short sentences, front-loaded with what is returned, then cost, then when to call, then the empty-table edge case. No sentence is filler and each adds a distinct decision-relevant fact.

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

Completeness5/5

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

For a simple read tool with one required parameter and no output schema, the description supplies everything needed: the return shape, the cost profile, the usage trigger, and the pathological case of a component with no props.

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?

The single parameter is fully documented in the schema (100% coverage), including its meaning as a registry slug and concrete examples. The description adds no further semantics about the slug, such as where it comes from or validation behavior, so the baseline of 3 applies.

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

Purpose5/5

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

Concrete verb plus resource: 'Return the prop table of one component', immediately followed by the exact contents (type, required, default, behavior). It also distinguishes itself from the heavier sibling by noting it is 'far smaller than the full source', so an agent can tell it apart from get_component without opening a schema.

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?

Explicit use cases are given: call it before writing JSX for a component you have not read, or to answer 'what can I configure on X'. The size contrast with the full source implies when to prefer this over the source-reading tool, but no sibling is named outright and there is no explicit when-not clause.

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