Skip to main content
Glama
lsd-so

LSD MCP Server

by lsd-so

use_trip

Execute a specific LSD trip by providing its identifier to access and process web data through SQL-like queries.

Instructions

Invokes a trip on LSD based on its identifier using the [ACCORDING TO] keywords.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trip_identifierYes

Implementation Reference

  • app.py:66-72 (handler)
    The core handler function that executes the 'use_trip' tool by connecting to the LSD database and running the SQL query 'ACCORDING TO {trip_identifier}', returning the fetched rows as a list of lists.
    def use_trip(trip_identifier: str) -> List[Dict[str, str]]:
        """Invokes a trip on LSD based on its identifier using the [ACCORDING TO] keywords."""
        conn = establish_connection()
        with conn.cursor() as curs:
            curs.execute(f"ACCORDING TO {trip_identifier}")
            rows = curs.fetchall()
            return [list(r) for r in rows]
  • app.py:65-65 (registration)
    The @mcp.tool() decorator registers the 'use_trip' function as an MCP tool.
    @mcp.tool()
  • app.py:66-66 (schema)
    The function signature defines the input schema (trip_identifier: str) and output schema (List[Dict[str, str]]). Note: return type is actually List[List[str]] based on implementation, but annotated as List[Dict[str, str]].
    def use_trip(trip_identifier: str) -> List[Dict[str, str]]:
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 mentions 'invokes a trip on LSD,' which suggests a mutation or action, but fails to describe key traits such as permissions required, side effects, error handling, or response format. The phrase '[ACCORDING TO] keywords' adds some context but is vague and insufficient for 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief with one sentence, which is appropriately sized for a simple tool. However, the phrase '[ACCORDING TO] keywords' is unclear and adds noise without value, reducing efficiency. It is front-loaded with the main action but could be more streamlined by omitting ambiguous elements.

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 (involving 'invoking' a trip on LSD), lack of annotations, no output schema, and low parameter coverage, the description is incomplete. It does not cover essential aspects like what the tool returns, error conditions, or prerequisites, making it inadequate for effective use by an AI agent without additional context.

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?

The input schema has 1 parameter with 0% description coverage, and the description does not add meaningful semantics beyond the schema. It references 'trip_identifier' indirectly but does not explain what this identifier is, its format, or how to obtain it. With low schema coverage, the description fails to compensate, leaving the parameter poorly documented.

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?

The description states the tool 'invokes a trip on LSD based on its identifier,' which provides a vague purpose with the verb 'invokes' and resource 'trip on LSD.' However, it lacks specificity about what 'invokes' means (e.g., starts, executes, triggers) and does not clearly differentiate from sibling tools like 'run_lsd' or 'search_trips,' leaving ambiguity in its exact function.

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 includes the phrase 'using the [ACCORDING TO] keywords,' which implies some context or method for usage, but it does not provide explicit guidance on when to use this tool versus alternatives like 'run_lsd' or 'search_trips.' There are no clear when/when-not instructions or named alternatives, resulting in minimal actionable guidance.

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/lsd-mcp'

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