Skip to main content
Glama

ToolRouter

by io.github.Humanleap

List Files

file_list
Read-onlyIdempotent

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

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral nuance by stating that an optional query changes the operation to semantic search. No contradictions with annotations exist.

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 a single sentence with no filler. It front-loads the core action, then immediately conveys semantic search behavior and the supported filters, making it efficient and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 100% schema coverage and read-only annotations, the description plus structured data fully support correct invocation. It conveys the two usage modes, available filters, and the non-destructive nature of the operation, which is sufficient for a list/search tool.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by clarifying that 'query' triggers semantic search and by naming the primary filters supported. It does not enumerate every parameter, but the schema covers the remaining ones well.

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 opens with 'List or search files', a specific verb and resource, and clarifies that an optional query triggers semantic search. This clearly distinguishes the tool from sibling tools like file_read, file_write, and file_delete, even without naming them.

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?

The description gives clear context: use it to browse files or run a semantic search by providing a query, with the listed filters available. It does not explicitly state when to prefer alternatives like file_read, but the list/search intent is clear enough for routing.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Tools are grouped by clear resource prefixes (account_, brain_, connector_, credential_, file_, job_, key_), and most actions have distinct purposes. A few boundaries overlap—brain_admin's lint action duplicates brain_lint, and account_preferences/setup/switch could momentarily confuse—but the descriptions resolve most ambiguity.

Naming Consistency3/5

The dominant pattern is resource_verb for actions (file_read, job_cancel, key_create) and resource_noun for state views (credits_balance, brain_settings, account_preferences), which is readable. However, exceptions like discover, use_tool, top_up_credits, and feedback_request_tool break the pattern, and the set is not consistently verb_noun.

Tool Count2/5

47 tools is well beyond the comfortable range; even though prefixes organize them, the agent faces a large selection surface with many narrowly scoped tools. A more consolidated set with action-based subcommands would be easier to navigate.

Completeness4/5

Core workflows are covered end-to-end: account setup and billing, connector and credential management, file CRUD, job polling, key lifecycle, brain knowledge management, and catalogue discovery/execution. Gaps are minor—outfit/persona/product/scene are list-only, connectors lack an update operation, and there is no explicit single-page brain get—but agents can generally work around them.

Resources