Skip to main content
Glama

List public source statuses

list_sources
Read-only

Check credential-presence status for clip sources without exposing secret values, so users can verify access availability before searching or retrieving clips.

Instructions

Read credential-presence status snapshot without exposing any values.

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

Output Schema

NameRequiredDescriptionDefault
kindNo
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description does add one genuinely useful disclosure beyond them: results are a point-in-time snapshot that never exposes credential values. It still says nothing about how many sources come back, ordering, or what a missing credential looks like.

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?

A single front-loaded sentence with no filler, and the privacy guarantee is placed where it will be read first. It is arguably over-compressed, since the one clause has to carry both the purpose and the safety note.

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?

A zero-parameter read tool with a full output schema and read-only annotations needs very little prose, and the two things an agent genuinely cannot infer, that this is a non-mutating snapshot and that values are withheld, are both stated. Nothing required to invoke it correctly is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The sentence makes no parameter claims that could conflict with the empty schema.

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

Purpose3/5

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

The description gives a verb ("Read") and an object ("credential-presence status snapshot"), but it never says it enumerates sources, nor what a "source" is. The title ("List public source statuses") and the name (list_sources) carry more of the purpose than the description does, and there is no signal separating it from the clip-oriented siblings.

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?

There is no when-to-use guidance, no prerequisite (e.g. call before search_and_import to verify credentials), and no named alternative. An agent must infer the call context entirely from the name and title.

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