Skip to main content
Glama
Sign In
recall-mcp

recall-mcp

by jaswanthsurya007-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_sources

See all documents in your knowledge base and the active search mode to understand what information is available.

Instructions

List the documents in the knowledge base and the active search mode.

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
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It only states the action but does not disclose traits like read-only nature, whether it lists all documents without filters, pagination behavior, or any side effects. For a simple list tool, this is minimal disclosure.

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 of 10 words, extremely concise with no wasted text. For a no-parameter tool, this is appropriately sized and front-loaded.

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?

The tool is low complexity with no parameters and an output schema exists (though not detailed here). The description is adequate but could be more complete by mentioning that it lists all documents (no filtering) or clarifying return format. Given the output schema, the description is minimally sufficient.

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?

There are no parameters (schema coverage 100%), so the description does not need to add param info. Baseline for 0 params is 4. The description is clear about what the tool does, which is sufficient.

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?

The description clearly states that the tool lists 'documents in the knowledge base' and 'the active search mode', specifying the verb (list) and resources. However, 'active search mode' is vague and not defined further, and it does not distinguish from siblings like search_documents which also deals with documents.

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?

No guidance is provided on when to use this tool versus alternatives such as search_documents (for searching) or get_document (for a specific document). The agent is left to infer that this tool should be used to get an overview, but exclusions or context are missing.

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

Deploy Server

Other Tools