Skip to main content
Glama

Best AI Things directory

Tools in a category

browse_category
Read-only

The newest AI tools in one directory category, each with its listing link.

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": {
      "category": "<category>"
    },
    "name": "browse_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 10).
pricingNoOnly tools with this pricing: free, freemium (free plan plus paid), paid, or contact (sales only).
categoryYesA category slug from list_categories, e.g. "video" or "software-development".

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=true and openWorldHint=false, so safety is covered. The description adds the 'newest' ordering and that each result carries a listing link, which is useful behavior beyond the annotations. It says nothing about pagination beyond the limit cap or what happens with an invalid slug.

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?

A single sentence with no filler, and the two most useful facts (newest ordering, listing link) are front-loaded. It is arguably too terse for a three-parameter tool, but nothing is redundant.

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 simple read-only browse tool with full schema coverage and no output schema, the description covers the core what and result shape. It omits the pricing filter and limit behavior and does not route the agent to search_tools or list_categories, which are the remaining gaps given the sibling set.

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 limit, pricing, and category are all documented in structured data, making 3 the baseline. The description only echoes the required category concept and adds no meaning about the pricing filter, limit default, or slug format.

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 resource and scope: the newest AI tools within one directory category, each returned with its listing link. The 'newest' ordering and 'listing link' return shape are concrete. It does not distinguish itself from siblings such as search_tools or list_categories, which is the only thing keeping it from 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?

Usage is only implied: the category-slug requirement plus the 'from list_categories' hint in the schema suggest the intended flow (list categories, then browse one). The description itself offers no explicit when-to-use or when-to-prefer-search_tools guidance, leaving the agent to infer the boundary.

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