Skip to main content
Glama
Sign In
agent-context-router

agent-context-router

by dakotafabro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Modules

list_modules

Lists all available policy modules on this machine and shows each module's load trigger, helping agents discover on-demand instruction modules without bloating AGENTS.md.

Instructions

List every policy module available on this machine, with the trigger that says when to load it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'List every ... on this machine' usefully discloses exhaustiveness and locality, but says nothing about safety, cost, or failure modes; the mention of the load trigger largely restates what the output schema already shows.

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?

One front-loaded sentence, no waste. Both clauses (what is listed, what is included) earn their place.

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 no-param, read-only enumeration with an output schema, the description covers scope and content adequately. The only gap is routing guidance relative to load_module, which matters because the two are easy to confuse.

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?

Zero parameters, so there is nothing to mis-specify and the baseline of 4 applies. The description correctly implies no filtering or pagination inputs exist.

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?

Specific verb and resource ('list every policy module') with an explicit scope ('available on this machine'). It reads as distinct from load_module (list vs. load), though it never names siblings directly.

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?

Use is only implied: listing modules so one can be chosen for loading. There is no statement of when to prefer this over load_module or search_context, and no prerequisites are given.

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