Skip to main content
Glama
lsd-so
by lsd-so

find_trips

Search for custom web data extraction trips in the LSD database to extend research and functionality through internetdata SDK.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • Core handler function that executes the find_trips logic: searches LSD trips via runLSD, maps to dynamic tools using toToolDefinition, registers them using registerTools, and returns the trip results.
    export const findTrips = async (server: McpServer, query: string) => {
      const result = await runLSD(`SEARCH "${query.replaceAll("\"", "'")}"`);
    
      registerTools(server, result.map(toToolDefinition));
      return result;
    };
  • src/trips.ts:37-49 (registration)
    Function that registers the 'find_trips' tool on the MCP server, including the input schema { query: z.string() } and the tool handler that invokes findTrips and returns formatted content response.
    export const applyTripsTool = (server: McpServer) => {
      server.tool("find_trips", { query: z.string() }, async ({ query }) => {
        const result = await findTrips(server, query);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result),
            },
          ],
        };
      });
    };
  • src/index.ts:16-16 (registration)
    Top-level call during server setup that triggers registration of the find_trips tool.
    applyTripsTool(server);
  • Helper utility that transforms an LSD trip database row into a dynamic MCP tool definition for use in findTrips.
    const toToolDefinition = (
      row: Record<string, any>,
    ): { name: string; description: string; tool: ToolCallback } => {
      return {
        name: row["NAME"],
        description: row["DESCRIPTION"],
        tool: async () => {
          const result = await runLSD(row["STATEMENT"]);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result),
              },
            ],
          };
        },
      };
    };
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/lsd-so/internetdata-mcp'

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