Skip to main content
Glama
Sign In

Locus

by com.paywithlocus
OverviewDiscussionsAdmin

Browse tool groups

list_tool_groups
Read-onlyIdempotent

Browse catalog categories and packs (curated endpoint bundles) to orient before search_apis. Lists only: it enables nothing (use request_tool_access) and calls nothing (use execute). Free.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size.
queryNoName filter.
cursorNoPrior next_cursor.
group_typeNoGroup type.all

Output Schema

NameRequiredDescriptionDefault
countNo
groupsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / group_type
      Added value: +{
+  "default": "all",
+  "description": "Group type.",
+  "enum": [
+    "all",
+    "category",
+    "pack"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / kind
      Removed value: -{
-  "default": "all",
-  "description": "Group type.",
-  "enum": [
-    "all",
-    "category",
-    "pack"
-  ],
-  "type": "string"
-}
  2. Changed7 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from a prior call with the same filters."New value: +"Prior next_cursor."
    • changedInput schema / properties / kind / description
      Previous value: -"Group kind filter; defaults to all."New value: +"Group type."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size: default 20, max 50."New value: +"Page size."
    • changedInput schema / properties / query / description
      Previous value: -"Optional case-insensitive name filter."New value: +"Name filter."
    • removedOutput schema / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / count / description
      Removed value: -"Groups in this page."
    • removedOutput schema / properties / groups / description
      Removed value: -"Categories and packs with executable counts."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds genuinely new context beyond those: the operation is free, and it is purely observational with no access-granting or execution side effects. It does not cover pagination behavior, but the output schema handles the return shape.

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?

Three short clauses, front-loaded with the purpose before the parenthetical disambiguation and the negative boundaries. Every sentence earns its place with no filler.

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?

For a read-only list tool with full schema coverage, rich annotations, and an output schema, the description supplies everything an agent needs: purpose, orientation role in the workflow, and explicit side-effect boundaries.

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, query, cursor, and group_type are already fully documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb (browse) with a specific resource (catalog categories and packs), and defines what a pack is ('curated endpoint bundles'). It explicitly names the sibling tools it is not: search_apis, request_tool_access, execute.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

States when to use it ('to orient before search_apis') and draws explicit negative boundaries: it enables nothing (use request_tool_access) and calls nothing (use execute). Both the condition and the alternatives are given.

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

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