Skip to main content
Glama
Sign In

ToolRouter

by io.github.Humanleap
OverviewDiscussionsAdmin

List Files

file_list
Read-onlyIdempotent

List or search files. Optional query triggers semantic search. Supports section, tags, plan_status, limit, cursor filters.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter to files matching ALL of these tags.
limitNoMax results (default 20, max 50).
queryNoNatural language search query. Omit to browse.
cursorNoPagination cursor from a previous file_list response.
contextNo"personal" (default) or "team:<id>".
sectionNoFilter by section. Omit to list all.
plan_statusNoFilter plans by status.
prompt_typeNoFilter prompts by type (only valid when section is "prompts").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description usefully adds that query switches the tool into semantic-search mode and that cursor enables pagination, but it says nothing about result volume, ordering, or what the payload contains.

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?

Three short, front-loaded sentences with no filler; the mode-switching behavior comes first, which is the most decision-relevant fact. Only nit is the minor mislabel of "cursor" as a filter.

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 an 8-parameter tool with no output schema and a fully documented schema, the description is adequate but thin: it neither explains the pagination contract nor the personal/team context switch, leaving the agent to read the schema for anything beyond the list/search distinction.

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%, so the schema already documents all 8 parameters including enums and defaults. The description merely re-lists a subset (section, tags, plan_status, limit, cursor) and omits context and prompt_type, adding almost nothing beyond the structured fields.

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 (list/search) and resource (files), and clearly distinguishes the two modes: browse by default, semantic search when query is present. It does not, however, differentiate itself from file_read or the other *_list siblings, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Optional query triggers semantic search" gives a genuine when-to-use signal for the search mode, and the filter list hints at narrowing. But there is no guidance on when to prefer file_read over this, when search is a poor fit, or how the context/team scoping should be chosen.

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

All ToolRouter 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