Skip to main content
Glama
Sign In
server-commands-rtk

server-commands-rtk

by Ev3lynx727
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_uri

Resolve scheme URIs to absolute file paths using registered root directories from environment variables.

Instructions

Resolve a scheme:// URI to an absolute file path. Uses schemes registered via MCP_RESOURCE_ROOTS env var (headquarters://, vaults://, etc.). scheme://. resolves to the base directory.

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": {
      "uri": "<uri>"
    },
    "name": "resolve_uri"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesURI to resolve, e.g. headquarters://docs/api.md or vaults://.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: resolves to absolute paths, uses registered schemes, and special handling of 'scheme://.' for the base directory. It does not cover error cases or missing schemes, but is adequate for the tool's simplicity.

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 wasted words. The most important information is front-loaded, making it easy to parse quickly.

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 the tool has only one parameter, no output schema, and low complexity, the description is complete enough. It explains purpose, usage dependency, and edge case (dot for base directory).

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 description coverage is 100%, providing a baseline of 3. The description adds value by giving explicit examples and the special case of 'scheme://.', 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 resolves a scheme:// URI to an absolute file path, using a specific verb and resource. It distinguishes itself from siblings which are about commands, cache, and file operations.

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 gives clear context about when to use (to resolve URIs) and mentions the dependency on MCP_RESOURCE_ROOTS env var. However, it does not explicitly state when not to use or provide alternatives, though siblings are unrelated.

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