Skip to main content
Glama

recommend_tool

Recommends the appropriate Fabric pattern tool based on your task description to enable AI-driven pattern execution within Cline workflows.

Instructions

Recommends the best Fabric pattern tool for a given task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe user's task description

Implementation Reference

  • The handler logic for executing the 'recommend_tool'. It extracts the task from input, simulates a Perplexity recommendation (currently hardcoded to 'summarize'), and returns the recommended tool name.
     if (request.params.name === "recommend_tool") {
       const task = String(request.params.arguments?.input || '');
    
       // Use Perplexity to recommend a Fabric pattern
       // Call the Perplexity MCP server to search for the best Fabric pattern
       let recommendedTool = "summarize"; // default tool
       try {
         const perplexityResult = await new Promise<any>((resolve, reject) => {
      //server.accessResource({
           //  serverName: "github.com/pashpashpash/perplexity-mcp",
           //  uri: `search?query=Recommend the best Fabric pattern tool for the task: ${task}. Choose from the following patterns: ${patterns.join(', ')}&detail_level=brief`
           //}).then((result: any) => {
           //  console.error('Perplexity recommendation:', result);
           //  if (result && result.content && result.content[0] && result.content[0].text) {
           //    recommendedTool = result.content[0].text;
           //  } else {
           //    console.error("Unexpected result format from perplexity-mcp:", result);
           //  }
           //  resolve(result);
           //}).catch((error: any) => {
           //  console.error("Error calling perplexity-mcp:", error);
           //  reject(error);
           //});
           console.error("Calling perplexity-mcp to recommend a tool");
    recommendedTool = "summarize";
           resolve({content: [{text: "summarize"}]});
         });
    
         return {
           content: [{
             type: "text",
             text: `Recommended tool: ${recommendedTool}`
           }]
         };
       } catch (error) {
         console.error("Error calling perplexity-mcp:", error);
         return {
           content: [{
             type: "text",
             text: `Error calling perplexity-mcp: ${error}`
           }]
         };
       }
     }
  • src/index.ts:68-82 (registration)
    Registers the 'recommend_tool' in the ListTools response by adding it to the tools array, including its description and input schema.
    // Add the recommend_tool
    tools.push({
      name: "recommend_tool",
      description: "Recommends the best Fabric pattern tool for a given task",
       inputSchema: {
         type: "object",
         properties: {
           input: {
             type: "string",
             description: "The user's task description"
           }
         },
         required: ["input"]
       }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'recommends' but does not clarify how recommendations are generated (e.g., based on criteria, algorithms, or data sources), whether it requires specific permissions, or what the output format entails. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-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?

Given the tool's complexity (a recommendation function with no annotations or output schema), the description is incomplete. It lacks details on how recommendations are made, what criteria are used, the format of the output, or any behavioral traits. This makes it inadequate for an agent to fully understand and use the tool effectively.

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 input schema has 100% description coverage, with the parameter 'input' documented as 'The user's task description.' The description adds no additional meaning beyond this, such as examples or constraints. According to the rules, when schema coverage is high (>80%), the baseline score is 3, which applies here.

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 tool's purpose: 'Recommends the best Fabric pattern tool for a given task.' It specifies the verb ('recommends') and resource ('Fabric pattern tool'), making the function understandable. However, with no sibling tools provided, it cannot demonstrate differentiation from alternatives, preventing a score of 5.

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 provides no guidance on when to use this tool versus alternatives, prerequisites, or specific contexts. It merely restates the tool's function without indicating appropriate scenarios or exclusions, which is insufficient for effective agent 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/augmentedivan/fabric-mcp-server'

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