Locus

Execute a Locus catalog tool

locus_execute

Run one Locus tool by name for a US address or place and get cited public records back: every fact names the agency source and date. Use it for a single question or re-run it for the addresses you follow to see what is newly on file. Free tools answer directly. Paid tools first return their exact price and accept payment in _meta["x402/payment"]; a place Locus does not cover returns a free diagnostic, never a paid guess. Install agent skill: npx @velinussage/locus-agent-skill add.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "locus_execute"
  }
}

Input Schema

Name	Required	Description
`args`	No	Alias of arguments.
`name`	No	Canonical Locus catalog tool name. Paid tools keep their hyphenated REST slugs.
`tool`	No	Alias of name.
`input`	No	Alias of arguments.
`arguments`	No	Arguments for the selected catalog tool (the tool's own inputSchema from locus_search_tools).

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / args

Added value: +{
+  "additionalProperties": {},
+  "description": "Alias of arguments.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

removedInput schema / properties / arguments / default
```
Removed value: -{}
```

changedInput schema / properties / arguments / description

Previous value: -"Arguments for the selected catalog tool."New value: +"Arguments for the selected catalog tool (the tool's own inputSchema from locus_search_tools)."

addedInput schema / properties / input

Added value: +{
+  "additionalProperties": {},
+  "description": "Alias of arguments.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / tool

Added value: +{
+  "description": "Alias of name.",
+  "minLength": 1,
+  "type": "string"
+}

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

Changed7 schema fields changedSep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / args

Removed value: -{
-  "additionalProperties": {},
-  "description": "Alias of arguments.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}

addedInput schema / properties / arguments / default
```
Added value: +{}
```

changedInput schema / properties / arguments / description

Previous value: -"Arguments for the selected catalog tool (the tool's own inputSchema from locus_search_tools)."New value: +"Arguments for the selected catalog tool."

removedInput schema / properties / input

Removed value: -{
-  "additionalProperties": {},
-  "description": "Alias of arguments.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}

removedInput schema / properties / tool

Removed value: -{
-  "description": "Alias of name.",
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "name"
+]
```

Changed7 schema fields changedSep 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / args

Added value: +{
+  "additionalProperties": {},
+  "description": "Alias of arguments.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

removedInput schema / properties / arguments / default
```
Removed value: -{}
```

changedInput schema / properties / arguments / description

Previous value: -"Arguments for the selected catalog tool."New value: +"Arguments for the selected catalog tool (the tool's own inputSchema from locus_search_tools)."

addedInput schema / properties / input

Added value: +{
+  "additionalProperties": {},
+  "description": "Alias of arguments.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / tool

Added value: +{
+  "description": "Alias of name.",
+  "minLength": 1,
+  "type": "string"
+}

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

First observedSep 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare open-world, non-read-only, non-destructive behavior. The description usefully adds cost gating, payment via _meta["x402/payment"], free direct answers, and free diagnostics for uncovered places, which materially reduces the risk of unexpected paid invocation.

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?

The core behavior is front-loaded and each sentence conveys useful operational context. The final plugin-install command is promotional and slightly diminishes focus, but the description remains compact and well structured.

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 generic dispatcher with no output schema, the description covers citations, free versus paid behavior, and uncovered-place handling. However, it omits the critical discovery path for valid tool names and does not clarify that arguments must match the selected tool's schema, leaving a notable gap for first-time use.

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 parameter meaning is already supplied by the schema, including name and argument aliases. The description adds the important payment metadata detail but does not explain how arguments relate to the selected tool's own inputSchema beyond what the schema field already says.

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 states a specific verb and resource: run one named Locus tool for a US address or place and return cited public records. It is clear enough to distinguish execution from discovery, though it does not explicitly name or contrast with locus_search_tools.

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

Usage Guidelines4/5

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

It gives concrete usage contexts: a single question, or re-running for followed addresses to see newly filed records. It also explains free-tool and paid-tool behavior, though it does not state prerequisites such as discovering valid tool names first.

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.

Execute a Locus catalog tool

Tool call template

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources