Skip to main content
Glama
thehzuo

web-gui-mcp

by thehzuo

get_artifact_schema

Retrieve the schema definition for a stored artifact by providing its pattern ID. Choose between minimal or full detail to get the exact structure needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pattern_idYes
schemaYes
example_minimalYes
guidanceYes

Implementation Reference

  • The main handler function for the 'get_artifact_schema' tool. It looks up the artifact pattern by pattern_id, calls artifact_schema() to get the JSON schema (minimal or full detail), and returns the schema along with the pattern's example_minimal and guidance.
    def get_artifact_schema_handler(input_data: GetArtifactSchemaInput) -> GetArtifactSchemaOutput:
        pattern = get_pattern(input_data.pattern_id)
        return GetArtifactSchemaOutput(
            pattern_id=pattern.id,
            schema=artifact_schema(detail=input_data.detail),
            example_minimal=pattern.example_minimal,
            guidance=pattern.guidance,
        )
  • Pydantic input/output schemas for the 'get_artifact_schema' tool. Input accepts pattern_id and detail (minimal/full). Output returns pattern_id, schema (aliased from schema_), example_minimal, and guidance.
    class GetArtifactSchemaInput(ToolBaseModel):
        pattern_id: str
        detail: Literal["minimal", "full"] = "minimal"
    
    
    class GetArtifactSchemaOutput(ToolBaseModel):
        pattern_id: str
        schema_: dict[str, Any] = Field(alias="schema")
        example_minimal: dict[str, Any]
        guidance: list[str]
  • Registration of the 'get_artifact_schema' tool as an MCP tool via the @mcp.tool() decorator inside register_tools(). Delegates to the handler function.
    @mcp.tool()
    def get_artifact_schema(input: GetArtifactSchemaInput) -> GetArtifactSchemaOutput:
        return get_artifact_schema_handler(input)
  • Helper function artifact_schema() that returns the JSON schema for ArtifactSpec. When detail='full', returns the entire schema. When detail='minimal', returns only title, type, required, and properties.
    def artifact_schema(detail: str = "minimal") -> dict[str, Any]:
        schema = ArtifactSpec.model_json_schema()
        if detail == "full":
            return schema
        return {
            "title": schema.get("title"),
            "type": schema.get("type"),
            "required": schema.get("required", []),
            "properties": schema.get("properties", {}),
        }
  • Helper function called by the handler to look up an ArtifactPattern by its id from the PATTERNS registry. Raises ValueError if pattern_id is unknown.
    def get_pattern(pattern_id: str) -> ArtifactPattern:
        try:
            return PATTERNS[pattern_id]
        except KeyError as exc:
            raise ValueError(f"Unknown artifact pattern: {pattern_id}") from exc
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thehzuo/gui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server