Skip to main content
Glama

List log sources

list_sources
Read-only

Lists the Chrome extensions, pages, and browsers that have sent console logs, so you can identify available log sources before filtering or waiting for entries.

Instructions

List the Chrome extensions and pages that have sent logs, and the browsers the stdout extension is sending them from.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add inventory semantics, which it does partially by naming the three kinds of sources returned. It says nothing about whether the result is empty when no logs exist, how sources are ordered or grouped, or whether 'pages' are identified by URL or tab id – context that matters for interpreting the output.

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?

A single front-loaded sentence with no filler. Every clause names a distinct category of returned source.

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

Completeness3/5

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

With no parameters and no output schema, the description must carry the full burden of explaining the return value. It enumerates the categories but not the shape or identifiers an agent would need to feed into a follow-up call, so it is adequate rather than complete.

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?

Zero parameters, so there is nothing for the description to clarify; baseline 4 applies. The description correctly implies the call is unfiltered and returns everything known.

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

Purpose4/5

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

Specific verb (list) plus concrete resource inventory: Chrome extensions, pages, and the browsers the stdout extension reports from. An agent can tell this is an enumeration of log producers rather than log entries, which separates it from siblings like get_logs, though it never names those siblings.

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?

Usage is only implied – an agent can infer this is a discovery step to find valid source names before calling get_logs or wait_for_log, but the description never states that or offers any when-not guidance. No prerequisites, no mention of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.