Skip to main content
Glama

Modulos AI Governance Platform

list_knowledge

Read-only

Lists everything else Modulos has published for AI agents: answers to common buyer questions, documents to share and further facts. Returns a title, a summary and a slug per entry. Use get_knowledge with the slug for the full entry.

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_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to one type: fact, qa (question and answer), comparison or document.
topicNoLimit to one topic, for example "security" or "pricing".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds value beyond that by disclosing the return shape (title, summary, slug per entry), which is exactly what an agent needs to plan a two-step list-then-fetch flow. No pagination or result-size behavior is mentioned, keeping it at a 4.

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?

Three short sentences with no wasted wording: purpose first, return shape second, sibling routing third. Each sentence carries distinct, actionable information.

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 two-optional-filter list tool with no output schema, the description covers purpose, return fields, and the follow-up call. The phrase "everything else" is slightly loose about scope boundaries, but otherwise nothing essential an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both optional filters (kind with an enum of fact/qa/comparison/document, topic with a slug pattern) are fully documented in the schema. The description adds no filter syntax or combination semantics of its own, so the baseline of 3 applies.

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?

States a specific verb ("lists") and resource ("everything Modulos has published for AI agents") and enumerates the content kinds: buyer Q&A answers, documents, facts. This clearly distinguishes it from get_knowledge, which retrieves a single full entry by slug.

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?

Explicitly routes the agent: use get_knowledge with the slug for the full entry, making the list-vs-fetch relationship unambiguous. It does not state when-not to use this tool or how it relates to non-knowledge siblings, but the primary alternative is covered.

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