URL Shortener MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shortenB | Shorten a URL using the cleanuri API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'shorten' has a single, clear purpose that cannot be confused with any other tool in this set.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'shorten' follows a clear verb-based pattern appropriate for its function, with no other tools to compare against for inconsistency.
A single tool for a URL shortener server is too few for the apparent scope, as it only covers shortening URLs without any complementary operations like retrieving, updating, deleting, or listing shortened URLs. This minimal set limits functionality and may cause agent failures in broader workflows.
The tool surface is severely incomplete for a URL shortener domain. While 'shorten' allows creation, there are no tools for retrieving, updating, deleting, or managing shortened URLs (e.g., get_url, list_urls, delete_url), creating significant gaps that will hinder agent performance in typical use cases.