Skip to main content
Glama
pydantic

Logfire MCP Server

Official

schema_reference

Retrieve the database schema for Logfire telemetry data, including table structures and column types, to construct efficient SQL queries.

Instructions

The database schema for the Logfire DataFusion database.

This includes all tables, columns, and their types as well as descriptions.
For example:

```sql
-- The records table contains spans and logs.
CREATE TABLE records (
    message TEXT, -- The message of the record
    span_name TEXT, -- The name of the span, message is usually templated from this
    trace_id TEXT, -- The trace ID, identifies a group of spans in a trace
    exception_type TEXT, -- The type of the exception
    exception_message TEXT, -- The message of the exception
    -- other columns...
);
```
The SQL syntax is similar to Postgres, although the query engine is actually Apache DataFusion.

To access nested JSON fields e.g. in the `attributes` column use the `->` and `->>` operators.
You may need to cast the result of these operators e.g. `(attributes->'cost')::float + 10`.

You should apply as much filtering as reasonable to reduce the amount of data queried.
Filters on `start_timestamp`, `service_name`, `span_name`, `metric_name`, `trace_id` are efficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The schema_reference async function that executes the tool logic. It fetches the database schema from the Logfire API (/v1/schemas) and converts it to SQL CREATE TABLE statements.
    async def schema_reference(ctx: Context[ServerSession, MCPState]) -> str:
        """The database schema for the Logfire DataFusion database.
    
        This includes all tables, columns, and their types as well as descriptions.
        For example:
    
        ```sql
        -- The records table contains spans and logs.
        CREATE TABLE records (
            message TEXT, -- The message of the record
            span_name TEXT, -- The name of the span, message is usually templated from this
            trace_id TEXT, -- The trace ID, identifies a group of spans in a trace
            exception_type TEXT, -- The type of the exception
            exception_message TEXT, -- The message of the exception
            -- other columns...
        );
        ```
        The SQL syntax is similar to Postgres, although the query engine is actually Apache DataFusion.
    
        To access nested JSON fields e.g. in the `attributes` column use the `->` and `->>` operators.
        You may need to cast the result of these operators e.g. `(attributes->'cost')::float + 10`.
    
        You should apply as much filtering as reasonable to reduce the amount of data queried.
        Filters on `start_timestamp`, `service_name`, `span_name`, `metric_name`, `trace_id` are efficient.
        """
        logfire_client = ctx.request_context.lifespan_context.logfire_client
        response = await logfire_client.client.get('/v1/schemas')
        schema_data = response.json()
    
        def schema_to_sql(schema_json: dict[str, Any]) -> str:
            sql_commands: list[str] = []
            for table in schema_json.get('tables', []):
                table_name = table['name']
                columns: list[str] = []
    
                for col_name, col_info in table['schema'].items():
                    data_type = col_info['data_type']
                    nullable = col_info.get('nullable', True)
                    description = col_info.get('description', '').strip()
    
                    column_def = f'{col_name} {data_type}'
                    if not nullable:
                        column_def += ' NOT NULL'
                    if description:
                        column_def += f' -- {description}'
    
                    columns.append(column_def)
    
                create_table = f'CREATE TABLE {table_name} (\n    ' + ',\n    '.join(columns) + '\n);'
                sql_commands.append(create_table)
    
            return '\n\n'.join(sql_commands)
    
        return schema_to_sql(schema_data)
  • Registration of the schema_reference tool with the FastMCP server via mcp.tool()(schema_reference).
    mcp.tool()(schema_reference)
  • The schema_to_sql nested helper function that transforms schema JSON data into SQL CREATE TABLE statements.
    def schema_to_sql(schema_json: dict[str, Any]) -> str:
        sql_commands: list[str] = []
        for table in schema_json.get('tables', []):
            table_name = table['name']
            columns: list[str] = []
    
            for col_name, col_info in table['schema'].items():
                data_type = col_info['data_type']
                nullable = col_info.get('nullable', True)
                description = col_info.get('description', '').strip()
    
                column_def = f'{col_name} {data_type}'
                if not nullable:
                    column_def += ' NOT NULL'
                if description:
                    column_def += f' -- {description}'
    
                columns.append(column_def)
    
            create_table = f'CREATE TABLE {table_name} (\n    ' + ',\n    '.join(columns) + '\n);'
            sql_commands.append(create_table)
    
        return '\n\n'.join(sql_commands)
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the SQL syntax is similar to Postgres but uses Apache DataFusion, explains how to access nested JSON, and advises on efficient filtering. No destructive actions are mentioned, which is appropriate for a read-only schema tool.

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 front-loaded with the purpose and provides detailed examples. While the SQL example takes space, it is relevant and informative. Could be slightly more concise, but overall well-structured.

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

Completeness5/5

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

Given the tool's purpose (providing schema), the description covers all necessary context: database type, SQL dialect, nested JSON access, and filtering advice. The output schema exists, so return values need not be detailed further.

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

Parameters4/5

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

The input schema has 0 parameters and 100% schema_description_coverage, so baseline is 4. The description adds value by explaining SQL syntax and operators for querying nested data, which aids in interpreting the schema output.

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

Purpose5/5

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

The description explicitly states that the tool provides the database schema for the Logfire DataFusion database, including tables, columns, types, and descriptions. This is a specific verb+resource combination that clearly distinguishes its purpose.

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 that this tool is used to understand the schema for crafting queries, but it does not explicitly state when to use it versus alternatives like arbitrary_query. No direct exclusions or alternative tool names are mentioned.

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/pydantic/logfire-mcp'

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