local-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Get effective permissions

get_permissions

Read-onlyIdempotent

Retrieve the effective root path, hard boundaries, and tool-use policy to confirm which filesystem operations are allowed before acting.

Instructions

Return the effective root, hard boundaries, and tool-use policy.

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": "get_permissions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 24, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The description states what information is returned ('effective root, hard boundaries, and tool-use policy'), which adds specificity beyond the annotations. Since readOnlyHint=true and idempotentHint=true already signal that this is a safe, non-mutating operation, the description aligns with that and provides additional detail about the response. No additional behavioral context (e.g., side effects, authorization needs) is mentioned, but given the annotations cover the safety profile, this is acceptable.

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 a single, compact sentence with no filler words. It directly names the key resources returned, and every word carries meaning. The structure is highly efficient and front-loaded with the core action. This meets the standard for a well-written, concise description.

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?

Given that the tool has no parameters and an output schema is present (as indicated by the context signals), the description does not need to elaborate on return format or edge cases. The one-sentence description fully covers what the tool does. The read-only and idempotent annotations further ensure the agent knows it is safe to call at any time. Nothing essential is missing.

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?

The tool has zero parameters, so per the rubric the baseline is 4. The description does not need to clarify any parameter meanings. The schema coverage is 100%, and there are no parameters to document. The description adds value by explaining what the response will contain, which is relevant even without inputs.

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 uses a specific verb ('Return') and identifies the exact resources ('effective root', 'hard boundaries', 'tool-use policy'). It clearly distinguishes this tool from the many other tools in the sibling list, which are focused on code execution, workflow management, or file operations. An agent can immediately understand the purpose without needing to inspect the schema.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it mention any context or exclusions. However, given the tool's obvious purpose as a read-only query for permissions, the usage is implied by the name and description. There are no competing sibling tools that appear to overlap in function, so the lack of explicit guidance is a minor gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.