Skip to main content
Glama
fasterv410

logflare-mcp

by fasterv410

List Logflare endpoints

list_endpoints

Retrieve all saved query endpoints for your Logflare account.

Instructions

List saved query endpoints for the account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:117-130 (registration)
    Registration of the 'list_endpoints' tool with the MCP server, including the handler that calls client.listEndpoints().
    server.registerTool(
    	'list_endpoints',
    	{
    		title: 'List Logflare endpoints',
    		description: 'List saved query endpoints for the account.',
    		inputSchema: {},
    	},
    	async () => {
    		try {
    			return text(await client.listEndpoints())
    		} catch (err) {
    			return errorText(err)
    		}
    	},
  • Handler function that executes when the tool is called; delegates to LogflareClient.listEndpoints().
    async () => {
    	try {
    		return text(await client.listEndpoints())
    	} catch (err) {
    		return errorText(err)
    	}
    },
  • Schema/description metadata for the tool, with empty inputSchema (no parameters required).
    {
    	title: 'List Logflare endpoints',
    	description: 'List saved query endpoints for the account.',
    	inputSchema: {},
    },
  • Client helper method that makes an HTTP GET request to /api/endpoints to list saved query endpoints.
    listEndpoints() {
    	return this.request<{ data: unknown[] }>('/api/endpoints')
    }
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as whether reading is safe, authentication needs, or side effects. It implicitly suggests a read operation but does not confirm.

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?

Single sentence with no wasted words. Front-loaded with action and object.

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

Completeness4/5

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

For a simple listing tool with no parameters, the description is largely complete. It could mention return format or confirm read-only behavior, but it covers the core purpose adequately.

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?

No parameters exist, and schema coverage is 100%, so baseline is 3. The description does not add parameter insight, but none is needed.

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 uses a specific verb 'List' and resource 'saved query endpoints' with scope 'for the account'. It clearly differentiates from sibling tools like list_sources (lists sources) and execute_query (query execution), so it stands out.

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?

No guidance on when to use this tool versus siblings like query_endpoint or list_sources. No exclusions or alternative recommendations provided.

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/fasterv410/logflare-mcp'

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