Skip to main content
Glama
appian-design

Design System MCP Server

refresh-sources

Manually refresh documentation sources to ensure access to current design system components, patterns, and layouts.

Instructions

Trigger manual refresh of documentation sources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'refresh-sources' tool registration and handler implementation.
    server.tool(
      "refresh-sources",
      "Trigger manual refresh of documentation sources",
      {},
      async () => {
        await sourceManager.refreshSources();
        
        return {
          content: [
            {
              type: "text",
              text: "Documentation sources refreshed successfully. Cache cleared and sources will be re-synced on next request.",
            },
          ],
  • The refreshSources method within SourceManager that performs the actual cache clearing.
    async refreshSources(): Promise<void> {
      this.cache = {};
      this.lastRefresh = Date.now();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'manual refresh' operation, implying it triggers an update process, but doesn't describe what happens during the refresh (e.g., data fetching, caching, notifications), how long it takes, whether it's idempotent, or what permissions are required. This leaves significant gaps for a mutation-like tool.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness2/5

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

For a tool that appears to trigger a mutation (refresh) with no annotations and no output schema, the description is insufficient. It doesn't explain what the refresh entails, what happens on success/failure, or what (if anything) is returned. Given the complexity implied by 'manual refresh', more context is needed for effective use.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't waste space on parameter details, earning a high baseline score for this dimension.

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 clearly states the action ('Trigger manual refresh') and the target ('documentation sources'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its siblings like 'get-content-sources' or explain how they relate, preventing a perfect score.

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?

The description offers no guidance on when to use this tool versus alternatives like 'get-content-sources' or 'search-design-system'. It doesn't mention prerequisites, timing considerations, or any context for when a manual refresh is needed versus relying on automatic updates.

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/appian-design/aurora-mcp'

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