Skip to main content
Glama
Sign In

Agent Module

by dev.agent-module
OverviewDiscussionsAdmin

query_knowledge

Read-onlyIdempotent

Retrieve structured knowledge from Agent Module verticals. Returns deterministic, validated knowledge nodes. Index layer always free. All 4 content layers available via trial key on ethics.

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": {
      "vertical": "<vertical>"
    },
    "name": "query_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoSpecific node ID to retrieve. Omit for root index.
tokenNoMembership or trial key (am_live_, am_test_, or am_trial_ prefix). Required for content layers on gated verticals.
verticalYesKnowledge vertical to query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavioral context: results are deterministic and validated, the index layer is always free, and content layers require a trial key on the ethics vertical. This adds value without contradicting the annotations.

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 concise (three sentences) and front-loaded with the core purpose. Each sentence adds distinct information: what it does, what it returns, and access/cost details. No unnecessary repetition.

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?

For a retrieval tool with no output schema, the description gives a reasonable overview but lacks detail on the structure of the returned knowledge nodes and the exact meaning of 'content layers' and 'index layer'. The enum of verticals is in the schema, but the description could better bridge the access model and expected results.

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?

The input schema already provides 100% description coverage for all three parameters, so the description does not need to re-explain them. However, the description's mention of 'index layer' and 'content layers' only loosely relates to the token and vertical parameters, and it does not clarify parameter-specific usage beyond the schema.

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 clearly states the tool's action ('Retrieve structured knowledge') and resource ('Agent Module verticals'), and mentions the output type ('deterministic, validated knowledge nodes'). This distinguishes it from sibling tools like check_status or get_trial_key, which serve different purposes.

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?

The description implies usage by describing what can be retrieved and the access conditions (index free, trial key on ethics), but it does not explicitly state when to use this tool versus alternatives, or provide any exclusions or prerequisites beyond the access note.

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

All Agent Module toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources