Skip to main content
Glama
hungnguyen1503

Renesas FSP MCP Server

manage_dependencies

Check FSP dependency compatibility and list versions for a target Renesas MCU platform.

Instructions

Manage FSP dependencies, versions, and compatibility matrix

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
platformNoTarget MCU platform

Implementation Reference

  • The main handler function for the manage_dependencies tool. It supports three actions: 'list' (lists available FSP versions), 'check_compatibility' (shows compatibility matrix for platforms), and 'get_versions' (shows supported versions for a platform).
    export const dependencyManagerHandler = async (args?: any) => {
      const action = args?.action || 'list';
      const platform = args?.platform || '';
    
      // FSP version history
      const versionHistory: Record<string, string> = {
        'v6.4.0': 'December 2025 - Latest stable release',
        'v6.3.0': 'October 2025 - Security fixes included',
        'v6.2.0': 'August 2025 - New peripheral drivers',
        'v6.1.0': 'June 2025 - RTOS improvements',
        'v6.0.0': 'April 2025 - Major architecture update'
      };
    
      // Platform compatibility matrix
      const compatibilityMatrix: Record<string, string[]> = {
        'RA6M3': ['v6.4.0', 'v6.3.0', 'v6.2.0'],
        'RA4E1': ['v6.4.0', 'v6.3.0', 'v6.1.0'],
        'RA8D1': ['v6.4.0', 'v6.2.0', 'v6.0.0'],
        'RA0E1': ['v6.3.0', 'v6.2.0', 'v6.1.0']
      };
    
      const result: any = {};
    
      switch (action) {
        case 'list':
          result.action = action;
          result.title = 'Available FSP Versions';
          result.data = Object.entries(versionHistory).map(([version, release]) => ({
            version,
            release_date: release
          }));
          break;
    
        case 'check_compatibility':
          result.action = action;
          result.title = `Compatibility Matrix for ${platform || 'All Platforms'}`;
          
          const platforms = Object.keys(compatibilityMatrix);
          const versions = [...new Set(Object.values(compatibilityMatrix).flat())];
          
          result.data = {
            headers: ['Platform', ...versions],
            rows: platforms.map(p => [
              p,
              ...versions.map(v => compatibilityMatrix[p]?.includes(v) ? '✅' : '❌')
            ])
          };
          break;
    
        case 'get_versions':
          result.action = action;
          result.title = `Version Information for ${platform || 'All Platforms'}`;
          
          const platformVersions = compatibilityMatrix[platform] || Object.values(compatibilityMatrix)[0];
          result.data = {
            platform,
            supported_versions: platformVersions,
            latest_version: 'v6.4.0',
            minimum_e2_studio: '2025-12.1+'
          };
          break;
    
        default:
          return {
            content: [
              { 
                type: "text",
                text: `Unknown action: ${action}. Available actions: list, check_compatibility, get_versions`
              }
            ]
          };
      }
    
      return result;
    };
  • Input schema definition for the manage_dependencies tool, defining 'action' (enum: list, check_compatibility, get_versions) and 'platform' (string) as input properties.
    {
      name: "manage_dependencies",
      description: "Manage FSP dependencies, versions, and compatibility matrix",
      inputSchema: {
        type: "object",
        properties: {
          action: {
            type: "string",
            enum: ["list", "check_compatibility", "get_versions"]
          },
          platform: {
            type: "string",
            description: "Target MCU platform"
          }
        }
      }
    },
  • src/index.ts:163-164 (registration)
    Registration of the manage_dependencies tool in the CallToolRequestSchema handler, routing to dependencyManagerHandler.
    case "manage_dependencies":
      return await dependencyManagerHandler(args);
  • Import statement for dependencyManagerHandler from the handlers/dependencies module.
    import { apiReferenceHandler } from "./handlers/api-reference.js";
Behavior1/5

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

No annotations provided, and description fails to disclose behavioral traits like safety, side effects, or required permissions. 'Manage' implies mutability but no details.

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?

Single concise sentence with no superfluous content. However, it lacks necessary detail but is efficiently structured.

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 with 2 params and no output schema, description fails to explain return values, behavior, or integration with sibling tools. Incomplete for reliable invocation.

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

Parameters2/5

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

Schema coverage is 50% (only platform described). Description adds no parameter details beyond schema, leaving action enum and platform usage unexplained.

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

Purpose3/5

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

Description states it manages FSP dependencies, versions, and compatibility matrix, which is a clear resource but uses vague verb 'manage'. It distinguishes from sibling tools like fsp_version and fsp_info by focusing on dependencies, but lacks specificity.

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?

No guidance on when to use this tool vs alternatives such as fsp_version or fsp_info. Agent receives no context for decision making.

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/hungnguyen1503/fsp-mcp'

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