Skip to main content
Glama

knowledge_sources

Read-only

Lists local documentation snapshots with record counts and last sync times, helping you verify available FiveM framework docs and their freshness before searching.

Instructions

List local documentation snapshots, record counts and last sync times

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": "knowledge_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish that the operation is read-only, non-destructive, and closed-world. The description adds useful local-snapshot scope and freshness-related metadata, but it does not clarify whether listing triggers a sync, how current the information is, or whether any sources are omitted.

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 single compact phrase front-loads the operation and then identifies the two metadata fields included. There is no redundant or unnecessary wording.

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 simple zero-argument listing tool, the description supplies enough information to understand and invoke it, while the annotations cover its safety profile. With no output schema, however, additional context about the result structure, snapshot freshness, and the tool's relationship to content-reading tools would make it more 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?

The tool has no parameters, so there is no argument syntax or semantics for the description to explain. The empty schema is sufficient for correct invocation, and the description appropriately focuses on the listed resources instead.

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 uses a specific verb and resource: it lists local documentation snapshots along with record counts and last sync times. This suggests an inventory/metadata role distinct from knowledge_read and knowledge_search, but it does not explicitly differentiate itself from 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 implied for inspecting available local documentation and its synchronization metadata. There is no explicit guidance on when to choose this tool over knowledge_read or knowledge_search, such as checking source availability or freshness before retrieving content.

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