Locus

Search APIs

search_apis

Read-onlyIdempotent

Find enabled catalog APIs by default, with prices and access state; filter for disabled APIs.

Input Schema

TableJSON Schema

Name	Required	Description
`pack`	No	Canonical curated-pack ID or an unambiguous live pack alias.
`limit`	No	Results: default 5, max 50.
`query`	No	Outcome or provider search phrase. Optional when category or pack is supplied.
`cursor`	No	Opaque next_cursor from a prior search with the same filters.
`enabled`	No	Filter to enabled or disabled endpoints. Defaults to true; pass "all" to include both, ranked enabled-first.
`category`	No	Canonical category ID or an unambiguous live category alias.
`include_facets`	No	Include bounded principal-scoped category and pack counts.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`query`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Results: default 10, max 50."New value: +"Results: default 5, max 50."
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / count / description
```
Removed value: -"Results in this page."
```
- removedOutput schema / properties / query / description
```
Removed value: -"Echo of the search phrase."
```
- removedOutput schema / properties / results / description
```
Removed value: -"Catalog entries with pricing and next step."
```

Changed8 schema fields changedSep 17, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Canonical category ID or an unambiguous live category alias.",
+  "maxLength": 120,
+  "type": "string"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque next_cursor from a prior search with the same filters.",
+  "maxLength": 500,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / enabled

Added value: +{
+  "description": "Filter to enabled or disabled endpoints. Defaults to true; pass \"all\" to include both, ranked enabled-first.",
+  "oneOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "const": "all",
+      "type": "string"
+    }
+  ]
+}

addedInput schema / properties / include_facets

Added value: +{
+  "description": "Include bounded principal-scoped category and pack counts.",
+  "type": "boolean"
+}

addedInput schema / properties / pack

Added value: +{
+  "description": "Canonical curated-pack ID or an unambiguous live pack alias.",
+  "maxLength": 120,
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Search phrase."New value: +"Outcome or provider search phrase. Optional when category or pack is supplied."

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Results in this page.",
+      "type": "integer"
+    },
+    "query": {
+      "description": "Echo of the search phrase.",
+      "type": "string"
+    },
+    "results": {
+      "description": "Catalog entries with pricing and next step.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact, the enabled-only default, but says nothing about result limits, ranking, or pagination beyond what the params already state.

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?

A single tight sentence that front-loads the default behavior before the exception. Every clause carries information and nothing is wasted.

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?

An output schema exists and the params are fully described, so the description need not explain return values. It adequately covers the default filtering model for a zero-required-param search tool, with only minor gaps around result limits and how filters combine.

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 fully documents all 7 parameters including the enabled default and the cursor semantics. The description merely restates the enabled default, adding no format, syntax, or interaction detail beyond the schema; baseline 3 applies.

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 and resource ("Find ... catalog APIs") plus the default scope (enabled only) and what is returned (prices, access state). It is clearly distinct from siblings like describe_api or list_calls in tone, though it never names an alternative explicitly.

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 clause "filter for disabled APIs" implies the main use case (broadening results), and the default hints at normal usage. However there is no explicit when-to-use/when-not guidance and no sibling tool is named as an alternative for a different filtering axis.

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

All Locus tools Inspect

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.