Locus

Pin endpoint

pin_endpoint

Idempotent

Add or remove one enabled endpoint as a typed tool on workspace MCP connections. The first pin requires explicit context-cost acknowledgement.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description
`slug`	No	provider/endpoint slug.
`pinned`	No	True when currently pinned.
`pinned_count`	No	Pinned endpoint count after this call.

Schema Changelog

Changes observed during successful MCP inspections.

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.2/5.0

Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, and the description complements this by noting the one-time context-cost acknowledgement requirement. It also implies that pinning affects model context on every connection, which is valuable behavioral information beyond what annotations provide. No contradiction.

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?

Two sentences with no filler. It front-loads the core function and puts the critical caveat second. Extremely efficient.

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 the tool's moderate complexity, a clear schema with good coverage, and an output schema, the description suffices. It covers the action, the key constraint (first pin acknowledgement), and context-cost impact. It lacks detail on consequences of unpinning, but that is minor.

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 coverage is 100%, so the schema already documents all parameters. The description adds minimal extra meaning, but the overall message is clear. Since coverage is high, baseline 3 is appropriate.

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 clearly states the tool adds or removes an enabled endpoint as a typed tool on workspace MCP connections. It uses precise verbs (add/remove) and specifies the resource (endpoint, MCP connections), distinguishing it from siblings like list_tool_groups or request_tool_access.

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?

The description is clear about the primary action and mentions a specific prerequisite for the first pin (context-cost acknowledgement). It doesn't explicitly state when NOT to use this tool or suggest alternatives, but it clearly implies it is for managing pins, which is sufficient for most usage scenarios.

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.