Skip to main content
Glama
Sign In
MCP CLI Chat

MCP CLI Chat

by prem-thatikonda29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

allow_path

Authorize the MCP CLI Chat server to access a specified file path during the current session, enabling file read and write operations.

Instructions

Grant the MCP server access to an absolute file path for this session

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "allow_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to allow (e.g. /Users/me/Desktop/file.txt)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Discloses session-scoped access but does not mention potential security implications, revocation, or success/failure conditions. No annotations to supplement.

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?

Single sentence, clear and direct, no redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool but context of when to use relative to siblings is missing. Does not state that this is likely needed before read/edit operations.

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?

Description of tool adds no extra meaning to the path parameter beyond the schema's own description. Coverage is 100%, so baseline 3.

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?

Clearly states the action (grant) and the object (access to an absolute file path) with session scope. Distinct from sibling doc-manipulation tools.

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?

Does not explicitly mention when to use or alternatives. Implied that it's a prerequisite for accessing files, but no direct guidance.

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

Deploy Server

Other Tools