Locus

Pin endpoint

pin_endpoint

Idempotent

Pin (pinned:true, the default) or unpin one enabled endpoint so it appears as its own typed tool on every MCP connection of this workspace instead of going through execute. Use for endpoints you call repeatedly. Each pin adds its schema to every session's context, so the first pin requires acknowledge_context_cost:true. Persistent and workspace-wide; does not enable or call the endpoint.

Input Schema

Name	Required	Description
`slug`	Yes	Exact provider/endpoint slug.
`pinned`	No	True to pin (default), false to unpin.
`acknowledge_context_cost`	No	Required once: pinned schemas use model context on every connection.

Output Schema

Name	Required	Description	Default
`slug`	No
`pinned`	No
`pinned_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026
- removedOutput schema / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / pinned / description
```
Removed value: -"True when currently pinned."
```
- removedOutput schema / properties / pinned_count / description
```
Removed value: -"Pinned endpoint count after this call."
```
- removedOutput schema / properties / slug / description
```
Removed value: -"provider/endpoint slug."
```

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "pinned": {
+      "description": "True when currently pinned.",
+      "type": "boolean"
+    },
+    "pinned_count": {
+      "description": "Pinned endpoint count after this call.",
+      "type": "integer"
+    },
+    "slug": {
+      "description": "provider/endpoint slug.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With annotations only covering the safety profile, the description adds substantial context: persistence, workspace-wide scope, the context-cost consequence on every session, and the first-pin acknowledge_context_cost:true prerequisite. These are behavioral traits not derivable from the annotations.

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?

Four dense sentences, front-loaded with the core action and default, then scope, then the prerequisite. No filler and nothing repeated.

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?

An output schema exists so return values need no explanation, and the description covers mutation semantics, scope, and the one-time acknowledgement prerequisite. Nothing needed to invoke it correctly is missing.

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 already documents all three parameters. The description reinforces the acknowledge_context_cost requirement and the pinned default, but adds little syntax or meaning beyond the schema's own descriptions.

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?

States a specific verb (pin/unpin), the resource (one enabled endpoint), and the precise effect (appears as its own typed tool on every MCP connection instead of going through execute). This clearly differentiates it from the execute sibling.

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?

Gives a clear when-to-use rule ('Use for endpoints you call repeatedly') and implicitly routes one-off calls to execute. It also states what the tool does not do ('does not enable or call the endpoint'), though it never names a negative alternative explicitly.

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.