Skip to main content
Glama
Sign In
Carnegie Mellon Web Kilt MCP Server

Carnegie Mellon Web Kilt MCP Server

Official
by cmu-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Get a Component

get_component
Read-only

Fetches a component's full documentation, required labels, classes, and copyable example markup. Use it to build pages with the correct kit release.

Instructions

One component's full description, what it requires (its labels), its classes and example markup to copy.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe component's id or name, from search_components, like "drop".
versionNoA kit release, like "0.4.0". Defaults to the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes further by disclosing the shape of the payload (description, labels, classes, example markup) in the absence of an output schema. It omits failure behavior when an id is unknown or how versions are resolved, which keeps it from a 5.

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?

A single front-loaded sentence that spends its words enumerating the returned artifacts rather than restating the title. It is a fragment without an explicit verb, which costs a little clarity, but nothing is wasted or padded.

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 simple two-parameter read-only tool with no output schema, the description adequately covers the returned content, which is the main unknown. The version parameter's default behavior is left entirely to the schema, which is acceptable given 100% coverage there.

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 both 'id' and 'version' fully documented in the schema including the version default. The description adds no syntax, format, or fallback detail beyond what the schema already provides, so the baseline 3 applies.

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 single-resource retrieval and enumerates what comes back: the component's description, required labels, classes, and example markup. The singular scope implicitly separates it from the plural sibling search_components, but no explicit verb or naming of the sibling makes the differentiation airtight.

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?

There is no statement of when to call this versus search_components or get_conventions, and no prerequisite or exclusion is given. The only workflow hint — that the id comes from search_components — lives in the schema, not the description. Usage is inferable only from 'example markup to copy'.

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

Deploy Server

Other Tools