Locus

Request tool access

request_tool_access

Create a short-lived approval link for one disabled (enabled:false) endpoint; send its URL to a human, who enables it. On an account your agent credential created that no person has claimed yet, it enables the endpoint at once (status enabled). Calls nothing; free.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Exact provider/endpoint slug returned by search.
`reason`	No	Why you need it, shown to the human.

Output Schema

Name	Required	Description
`slug`	No
`status`	No	already_enabled, enabled, pending_human_approval, approved, denied, or expired.
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "Why you need it, shown to the human.",
+  "type": "string"
+}

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / request_id
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / status / description

Previous value: -"already_enabled or pending_human_approval."New value: +"already_enabled, enabled, pending_human_approval, approved, denied, or expired."

Changed2 schema fields changedOct 7, 2026
- removedOutput schema / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / slug / description
```
Removed value: -"provider/endpoint slug."
```
AddedSep 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent, closed-world), the description discloses that the grant is short-lived, that approval is human-mediated in the normal case, and that an unclaimed agent-created account enables immediately. 'Calls nothing; free' rules out upstream invocation and billing side effects, which is genuinely useful context.

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?

Two dense sentences with the primary case front-loaded and the exception second; no filler. The telegraphic clauses ('status enabled', 'Calls nothing; free') are terse but readable, and nothing appears wasted.

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?

An output schema exists, so return values need not be explained, and the description covers both outcome branches of calling it. Minor gaps remain: behavior when the endpoint is already enabled, or what happens when the link expires or is denied.

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%, and both the exact provider/endpoint slug pattern and the 'reason' field (shown to the human) are already documented in the schema. The description reinforces that exactly one endpoint is targeted but adds no syntax or format detail beyond the schema.

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 concrete verb and resource: creating a short-lived approval link for a single disabled endpoint, plus the alternate auto-enable path. It is clearly distinct from execution-oriented siblings like execute or run_task, though it never names any sibling explicitly.

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?

Usage is implied by the scoping constraint ('one disabled (enabled:false) endpoint'), so an agent can infer this is the path when an endpoint is unavailable. It gives no explicit when-not guidance and does not point at alternatives such as execute, describe_api, or search_apis for other cases.

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.