Skip to main content
Glama

Browse Pool

neuron_browse_pool
Read-onlyIdempotent

Browse the shared marketplace pool of published bots, tools, knowledge bases, and reflections with optional filtering by type, category, tags, or search query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
tagsNoFilter by tags (comma-separated list, e.g., 'ai,chatbot')
typeNoFilter by resource type
limitNoNumber of items per page (default: 20)
queryNoFree-text search query to filter pool items by name or description
categoryNoFilter by category name
featuredNoWhen true, return only featured items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Filter by resource type (e.g., 'bot', 'tool', 'knowledge_base', 'reflection')"New value: +"Filter by resource type"
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "knowledge_base",
      +  "bot_template",
      +  "tool_template",
      +  "reflection_pack"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds that browsing includes optional filtering, but does not disclose additional behavioral traits beyond what annotations provide.

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 concise sentence that front-loads the action and resource, with no unnecessary words.

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?

The description covers the main purpose and filtering options adequately. Minor gaps include lack of explanation about pagination defaults or return format, but schema descriptions partially compensate.

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?

All 7 parameters have descriptions in the schema (100% coverage). The description summarizes filtering options but does not add meaning beyond the schema, such as format or defaults.

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?

The description clearly states the tool browses a shared marketplace pool of specific resource types with filtering options. However, it does not differentiate from the sibling tool 'neuron_browse_list_pool', which likely serves a similar purpose.

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 for browsing and filtering pool items but provides no explicit guidance on when to use this tool versus alternatives or what prerequisites are needed.

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