Skip to main content
Glama
fasterv410

logflare-mcp

by fasterv410

List Logflare sources

list_sources

List log streams accessible to your API key. View all configured log sources for monitoring.

Instructions

List all sources (log streams) accessible to the configured API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:40-54 (registration)
    Registration of the 'list_sources' tool on the MCP server with schema and handler.
    server.registerTool(
    	'list_sources',
    	{
    		title: 'List Logflare sources',
    		description: 'List all sources (log streams) accessible to the configured API key.',
    		inputSchema: {},
    	},
    	async () => {
    		try {
    			return text(await client.listSources())
    		} catch (err) {
    			return errorText(err)
    		}
    	},
    )
  • Schema definition for list_sources: title, description, and empty input schema (no parameters).
    {
    	title: 'List Logflare sources',
    	description: 'List all sources (log streams) accessible to the configured API key.',
    	inputSchema: {},
  • Handler function that calls client.listSources() and formats the response.
    async () => {
    	try {
    		return text(await client.listSources())
    	} catch (err) {
    		return errorText(err)
    	}
    },
  • Helper method on LogflareClient that performs the HTTP GET request to /api/sources.
    listSources() {
    	return this.request<{ data: unknown[] }>('/api/sources')
    }
Behavior3/5

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

With no annotations, the description provides minimal behavioral info: it lists only sources accessible to the API key. It does not disclose side effects, rate limits, or data volume, which is acceptable for a simple read-only list operation but lacks depth.

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?

The description is a single sentence that concisely conveys the purpose without unnecessary words, front-loading the key information.

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?

For a parameterless list tool, the description adequately covers what the tool does and its scope, making it complete enough for typical use cases.

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 zero parameters, so the description adds value by clarifying the scope of the list (accessible to the API key). Baseline for no parameters is 4; the description meets it.

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 clearly states the tool lists all sources (log streams) accessible to the configured API key, using a specific verb and resource, and implicitly distinguishes from sibling tools like get_source or get_recent_events which target specific items.

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 when to use this tool (to list all available sources) but does not explicitly state when not to use it or provide alternatives. Usage context is inferred rather than stated.

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