Skip to main content
Glama

encodeUrl

Convert input data into URL-encoded format using the encoding tool in the MCP server, ensuring compatibility with web standards. Ideal for processing strings in URLs.

Instructions

Encode input data to URL-encoded format

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesData to encode

Implementation Reference

  • The async handler function that URL-encodes the input using encodeURIComponent and returns the encoded string in MCP content format.
    handler: async ({ input }: { input: string }) => {
      const encoded = encodeURIComponent(input);
      return {
        content: [
          {
            type: 'text',
            text: encoded
          }
        ]
      };
    }
  • Input schema defining a required 'input' string parameter for the tool.
    inputSchema: {
      type: 'object',
      properties: {
        input: {
          type: 'string',
          description: 'Data to encode'
        }
      },
      required: ['input']
    },
  • Full tool registration object for encodeUrl, exported as part of encodingTools, which is later included in the main allTools object.
    encodeUrl: {
      name: 'encodeUrl',
      description: 'Encode input data to URL-encoded format',
      inputSchema: {
        type: 'object',
        properties: {
          input: {
            type: 'string',
            description: 'Data to encode'
          }
        },
        required: ['input']
      },
      handler: async ({ input }: { input: string }) => {
        const encoded = encodeURIComponent(input);
        return {
          content: [
            {
              type: 'text',
              text: encoded
            }
          ]
        };
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool encodes data but doesn't mention any behavioral traits such as error handling, performance characteristics, or side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it operates beyond the basic function.

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 that directly states the tool's function without any unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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 the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally adequate but lacks depth. It covers the basic purpose but doesn't address usage context, behavioral details, or output expectations, leaving room for improvement in completeness for effective agent use.

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?

The schema description coverage is 100%, with the single parameter 'input' documented as 'Data to encode'. The description adds no additional meaning beyond this, as it only reiterates the encoding action without detailing parameter constraints or usage. With high schema coverage, the baseline score of 3 is appropriate.

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 ('encode') and resource ('input data') with the specific format ('URL-encoded format'). It distinguishes from siblings like encodeBase64 and encodeHtml by specifying the encoding type, though it doesn't explicitly contrast them. The purpose is unambiguous but lacks explicit sibling differentiation.

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 like encodeBase64 or encodeHtml, nor does it mention any prerequisites or context for usage. It simply states what the tool does without indicating appropriate scenarios or exclusions.

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