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 10, 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
`count`	No	Results in this page.
`query`	No	Echo of the search phrase.
`results`	No	Catalog entries with pricing and next step.

Schema Changelog

Changes observed during successful MCP inspections.

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

A4/5.0

Behavior4/5

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

Annotations already mark the operation as read-only and idempotent, so the description adds value by disclosing the default result scope ('enabled catalog APIs by default') and that disabled APIs can be included. This is useful behavioral context beyond the structured hints.

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 tightly worded sentence that puts the main action first and communicates default behavior plus filtering capability without any filler.

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?

With a rich input schema, output schema, and safety annotations, the description is mostly sufficient. Its only notable gap is the absence of any guidance on when to use sibling tools, but an agent can still correctly invoke this tool from the description alone.

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%, and every parameter already has a clear meaning in the schema. The description reinforces the enabled-API default but does not add new semantic information about the parameters beyond what the schema provides.

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 states a specific verb and resource ('Find enabled catalog APIs') and adds concrete scope: results include prices and access state and can be filtered to disabled APIs. This clearly distinguishes search_apis from siblings like describe_api or execute.

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 conveys the core use case—searching catalog APIs with an enabled/disabled filter—but does not explicitly say when to prefer it over alternatives such as describe_api or pin_endpoint. The usage context is clear enough to infer, but no alternatives or exclusions are named.

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.