Skip to main content
Glama

Modulos AI Governance Platform

get_knowledge

Read-only

Returns one published knowledge entry in full: the answer to a question, the structured data of a fact, or the summary and link of a document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesEntry slug as returned by list_knowledge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/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 covered. The description adds genuine context beyond that: results are restricted to 'published' entries and the payload varies by entry type. It says nothing about behavior when a slug is missing or unpublished.

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?

One front-loaded sentence with no filler, and the enumeration of return shapes is efficient. Slightly dense phrasing ('in full: the answer to a question, the structured data of a fact, or the summary and link of a document') costs a little readability.

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 read-only, one-parameter lookup with no output schema, the description covers the variable return shape, which is the main unknown an agent faces. The remaining gap is error/not-found behavior, which is minor for this tool's complexity.

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 the single slug parameter is fully documented there, including format constraints, so the baseline of 3 applies. The description adds no additional meaning about the identifier beyond what the schema states.

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?

States a specific verb and resource ('Returns one published knowledge entry') and enumerates the three content shapes (answer, structured fact data, document summary+link). It does not name or distinguish itself from siblings such as list_knowledge, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance. Nothing tells the agent to call list_knowledge first to obtain a slug versus using check_fit or get_trust_evidence for other question types; the only discovery hint lives in the schema, not the description.

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