Skip to main content
Glama
clarenous
by clarenous

get_tools

Retrieve available tools and workflows from the VeyraX platform to access their methods, parameters, and capabilities for integration.

Instructions

"Use this tool to retrieve a list of available tools from the Veyrax API. This will return dynamic tools that user has access to. You can use this tool to get the list of tools, method names and parameters, and then use tool_call tool to call the tool with the provided parameters. This method also returns all flows with name and id that user has access to (if any). "

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesQuery question that you want find answer for. Try to ALWAYS provide this field based on conversation with user. Could be your reasoning for calling tool.
toolYesGuess the tool name. Use explicit information based on the user's request or make an educated guess. It will be used for vector search for identifying the most relevant tools.

Implementation Reference

  • The execute method of GetToolsTool that handles the tool logic: constructs URL with optional 'question' and 'tool' query params, fetches from Veyrax API '/get-tools', formats response as MCP content block.
    async execute({ question, tool }: z.infer<typeof this.schema>) {
      try {
        let url = '/get-tools';
        const params = new URLSearchParams();
        
        if (question) params.append('question', question);
        if (tool) params.append('tool', tool);
        
        if (params.toString()) {
          url += `?${params.toString()}`;
        }
        
        const { data } = await veyraxClient.get(url);
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw error;
      }
    }
  • Input schema using Zod: 'question' (string, conversation context/reasoning) and 'tool' (string, for filtering tools). Defines validation for tool parameters.
    schema = z.object({
      question: z.string()
        .describe("Query question that you want find answer for. Try to ALWAYS provide this field based on conversation with user. Could be your reasoning for calling tool."),
      tool: z.string()
        .describe("Guess the tool name. Use explicit information based on the user's request or make an educated guess. It will be used for vector search for identifying the most relevant tools.")
    });
  • src/index.ts:13-13 (registration)
    Registers the GetToolsTool with the MCP server in the main entry point.
    new GetToolsTool().register(server);
  • TypeScript interface for the get_tools response: object mapping tool names to their methods and parameters.
    export interface GetToolsResponse {
      tools: {
        [toolName: string]: Tool;
      };
    }
  • src/index.ts:4-4 (registration)
    Import statement for GetToolsTool used in registration.
    import { GetToolsTool } from "./tools/get-tools";
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. It mentions that the tool returns 'dynamic tools that user has access to' and 'all flows with name and id that user has access to (if any),' which adds some behavioral context about access control and conditional returns. However, it lacks details on rate limits, error handling, or what 'dynamic tools' entails, leaving gaps for a tool that retrieves system metadata.

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?

The description is appropriately sized with four sentences that are front-loaded with the core purpose. Each sentence adds value: the first states the purpose, the second clarifies access and dynamics, the third explains usage in a workflow, and the fourth notes the inclusion of flows. There's minimal redundancy, though it could be slightly more streamlined.

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

Completeness3/5

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

Given the complexity of retrieving system tools and flows, no annotations, and no output schema, the description provides basic purpose and usage but lacks details on return format, pagination, or error cases. It's adequate for a read operation but incomplete for guiding an agent on handling the response or understanding limitations.

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 description coverage is 100%, so the schema already documents both parameters ('question' and 'tool') with descriptions. The description doesn't add any meaning beyond what the schema provides regarding parameters; it focuses on the tool's purpose and usage instead. This meets the baseline of 3 when schema coverage is high.

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: 'retrieve a list of available tools from the Veyrax API' and mentions it also returns flows. It specifies the verb ('retrieve') and resource ('list of available tools'), but doesn't explicitly differentiate from sibling tools like 'get_flow' which presumably retrieves a specific flow rather than a list of tools and flows.

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

Usage Guidelines3/5

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

The description implies usage context by stating 'You can use this tool to get the list of tools... and then use tool_call tool to call the tool with the provided parameters,' suggesting a workflow. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_flow' or provide clear exclusions. The guidance is present but not comprehensive.

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/clarenous/veyrax-mcp'

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