Skip to main content
Glama
knewstimek

agent-tool

by knewstimek
OverviewSchemaRelated ServersScoreDiscussions
Go
Local

set_config

Change runtime configuration for file encoding, size limits, symlinks, workspace, SSRF policies, and network options. View current settings by calling without arguments.

Instructions

Changes agent-tool runtime configuration. Supports: fallback_encoding, encoding_warnings, max_file_size_mb, allow_symlinks, workspace. SSRF policy: allow_http_private, allow_mysql_private, allow_redis_private, allow_ssh_private. Network: enable_doh (DNS over HTTPS), enable_ech (Encrypted Client Hello). Call with no arguments to view current configuration. Example: set fallback_encoding to "EUC-KR" for Korean legacy projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fallback_encodingNoSet the fallback encoding for files when auto-detection fails. Examples: EUC-KR, Shift_JIS, ISO-8859-1. Empty = no change
encoding_warningsNoEnable/disable encoding detection warning messages in tool results. Default: true
max_file_size_mbNoMaximum file size in MB that read/edit/grep tools will accept. Min: 1, Default: 50
allow_symlinksNoAllow creating symlinks when extracting archives. Default: false (skipped for security)
workspaceNoSet the default workspace/project root directory. Used by glob when no explicit path is given. Must be an absolute path to an existing directory
allow_http_privateNoAllow webfetch/download/httpreq to access private IPs (127.x, 192.168.x, 10.x). Default: false (blocked). Cloud metadata IPs always blocked
allow_mysql_privateNoAllow mysql tool to access private IPs. Default: true. Cloud metadata IPs always blocked
allow_redis_privateNoAllow redis tool to access private IPs. Default: true. Cloud metadata IPs always blocked
allow_ssh_privateNoAllow ssh/sftp tools to access private IPs. Default: true. Cloud metadata IPs always blocked
enable_dohNoEnable DNS over HTTPS globally for webfetch/download/httpreq/dnslookup. Default: true. Per-request no_doh/use_doh can still override
enable_echNoEnable Encrypted Client Hello globally for webfetch/download/httpreq. Default: true. Per-request no_ech can still override

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions 'Changes' and lists effects of parameters, but omits details like persistence across sessions, authentication requirements, or side effects on other tools. The behavioral disclosure is adequate but not comprehensive.

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 concise (4 sentences) and well-structured: purpose, parameter categories, usage hint, and example. No wasted words; front-loaded with core information.

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?

Given 11 parameters, no output schema, and no annotations, the description covers purpose and categories but lacks return value format, error handling, or persistence details. It mentions viewing config but not its structure. Somewhat incomplete for a complex configuration tool.

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?

Schema coverage is 100% with detailed descriptions (defaults, examples, constraints). The description adds value by grouping parameters into categories (SSRF policy, Network) and providing a concrete example (EUC-KR for Korean projects), which enhances understanding beyond the schema.

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's purpose: 'Changes agent-tool runtime configuration.' It lists specific config categories and parameters, leaving no ambiguity. The tool's function is distinct from siblings like 'firewall' or 'sysinfo'.

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 provides usage guidance: 'Call with no arguments to view current configuration' and shows an example. It does not explicitly compare to alternatives or state when not to use, but the purpose is self-contained enough for an agent to infer usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/knewstimek/agent-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server