Locus

Execute a Locus catalog tool

locus_execute

Run one Locus catalog tool by name after locus_search_tools or a known tool name. Search and looking are free; this call may charge via MCP-native x402. Free tools return cited official-source primitives; paid tools return payment-required results and accept retry payment in _meta["x402/payment"]. Unsupported places return diagnostics instead of paid guesses. Do not use this for web scrape, LinkedIn, or generic fetch. Install agent skill: npx @velinussage/locus-agent-skill add.

Input Schema

TableJSON 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

A4.3/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries most of the behavioral burden. It discloses x402 payment requirements, free vs. paid return behavior, retry-payment mechanism in _meta, and diagnostic fallback for unsupported tools. This exceeds what the annotations provide and gives real operational detail. It doesn't mention rate limits or auth, but the disclosed behavioral traits are substantial.

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 dense but well-structured: it front-loads the core action, then covers pricing/behavior, exclusions, and a setup hint. Every sentence adds unique value, and it is concise given the complexity.

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?

Given there is no output schema, the description covers the main behavioral contract: what to call, what happens for free vs paid tools, and how to handle retry. It does not describe the exact shape of return values beyond cited sources vs payment-required, and it doesn't mention error handling for invalid names other than 'diagnostics'. For a tool with a sibling discovery tool and no output schema, this is fairly complete, but lacks explicit return-value details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter has a description. The description adds context about which parameter to use (name vs tool alias) for selecting the catalog toolched. It clarifies that the 'arguments' parameter carries the tool's own inputSchema, which is critical for using the tool. A 5 would require more explicit guidance on required parameter combinations or defaults, but the schema plus description is strong.

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 ('Run') and resource ('one Locus catalog tool by name'), and distinguishes itself from the sibling locus_search_tools by clarifying that search tools are separate. It could be slightly clearer about what exactly 'execute' means in terms of catalog tool behavior, but the core purpose is evident.

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?

Explicitly says when to use: after locus_search_tools or with a known tool name. It also says what not to use it for ('Do not use this for web scrape, LinkedIn, or paid guesses') and explains the search vs. execute separation. This is strong guidance for an agent.

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

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources