Skip to main content
Glama

list_sources

Read-only

List what the user has connected: calendars (id, account, work or private, whether it blocks planning, whether only events the user created there block, whether it receives busy copies, read-only ones) and integrations such as Jira and GitHub with their status. Call this first when you are unsure where to look for context, or before telling the user something is not connected.

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 observed

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint=true and destructiveHint=false annotations already establish the safety profile, so the description's main added value is disclosing the richness of the returned connection data (including read-only calendars and busy-copy flags). It says nothing about authentication requirements, latency, or whether integrations are queried live from third-party services, which are the remaining behavioral unknowns for a discovery call.

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?

Two sentences, front-loaded with the action and followed by the practical trigger. The long parenthetical enumerating calendar attributes is information-dense but slightly heavy and could have been a short bullet list; still, every clause conveys real attribute detail rather than filler.

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?

With zero parameters, no output schema, and read-only annotations, the description carries most of the informational burden, and it does describe the shape of returned calendar entries. The integration side is left vague ('with their status'), so an agent cannot fully anticipate what integration records contain, but this is a minor gap for a discovery tool.

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 no schema semantics for the description to supplement. The baseline of 4 applies; the description correctly implies the call is unscoped and global to the user's account.

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 and resource ('List what the user has connected') and then enumerates the two resource families: calendars with their attributes (id, account, work/private, blocking behavior, busy copies, read-only) and integrations like Jira and GitHub with status. This is concrete enough to distinguish it from siblings such as list_tasks or list_habits, which enumerate objects rather than connection/permission state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit trigger conditions ('Call this first when you are unsure where to look for context, or before telling the user something is not connected'), which is genuinely actionable guidance that prevents false-negative claims. It stops short of naming an alternative tool or stating when not to call it, so it lands at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources