Skip to main content
Glama

List sources

list_sources
Read-only

Lists connected data sources and the tables and columns the AI is allowed to access, so you can verify what Portward exposes before querying.

Instructions

List the connected sources with the tables and columns the AI may use.

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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds genuine behavioral value by disclosing the shape and scoping of the result: it returns tables and columns, filtered to what the AI is allowed to use, which implies permission-based filtering. It says nothing about ordering, volume, or how empty results appear.

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 sentence with no filler, and the key information — what is listed and what the listing contains — is front-loaded. Nothing in the sentence is redundant with the title.

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 zero-parameter read-only enumeration with no output schema, the description adequately covers what comes back at a high level: sources, tables, and columns. A brief note on ordering or typical result size would make it fully self-sufficient, but little is missing for correct invocation.

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 there is nothing for the description to disambiguate; the baseline for a no-argument tool applies. The description correctly implies the tool takes no input, since it is a plain enumeration.

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?

States a specific verb and resource ("List the connected sources") and adds scope: the returned tables and columns are only those the AI is permitted to use. That distinguishes it from a mutating sibling like add_source or remove_source, though it does not explicitly contrast with describe_source, which likely returns similar metadata for one source.

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. The phrase "the AI may use" hints that this is the discovery step before querying, but the description never states when to prefer this over describe_source or add_source, nor any prerequisites. An agent can infer the intent but gets no explicit routing guidance.

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