Skip to main content
Glama

decodeUrl

Decode URL-encoded data using this tool to restore original text or parameters. Ideal for processing encoded inputs quickly and accurately.

Instructions

Decode URL-encoded input data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesData to decode

Implementation Reference

  • The asynchronous handler function that decodes the input URL-encoded string using decodeURIComponent and returns it as text content in MCP format.
    handler: async ({ input }: { input: string }) => {
      const decoded = decodeURIComponent(input);
      return {
        content: [
          {
            type: 'text',
            text: decoded
          }
        ]
      };
    }
  • The input schema defining the expected 'input' parameter as a string for the decodeUrl tool.
    inputSchema: {
      type: 'object',
      properties: {
        input: {
          type: 'string',
          description: 'Data to decode'
        }
      },
      required: ['input']
    },
  • src/index.ts:27-33 (registration)
    Combines and registers encodingTools (including decodeUrl) with other toolsets into allTools, which is used by the MCP server's listTools and callTool request handlers.
    const allTools: ToolKit = {
      ...encodingTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the operation ('Decode') but doesn't describe what happens with invalid input (e.g., malformed URL encoding), whether it's idempotent, or any error handling. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. This is an excellent example of conciseness for a simple tool.

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?

For a simple decoding tool with one parameter and no output schema, the description covers the basic purpose adequately. However, it lacks context about error cases, output format (e.g., decoded string), and differentiation from similar tools, which would be helpful given the sibling tools performing related 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?

Schema description coverage is 100%, with the parameter 'input' documented as 'Data to decode'. The description adds no additional semantic context beyond this, such as examples of URL-encoded strings or formatting requirements. The baseline score of 3 reflects adequate but minimal value added over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Decode') and resource ('URL-encoded input data'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'decodeBase64' or 'decodeHtml', which perform similar decoding operations on different encoding formats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'decodeBase64' for base64 decoding or 'decodeHtml' for HTML entity decoding, nor does it specify scenarios where URL decoding is appropriate (e.g., handling encoded query parameters).

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

Related 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/MissionSquad/mcp-helper-tools'

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