Skip to main content
Glama
noisysocks

Autoconsent MCP

by noisysocks
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

reload

Refresh the current web page to test consent management platforms and rules in a browser automation environment.

Instructions

Reload the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:220-231 (handler)
    Handler logic for the 'reload' tool within the handleToolCall switch statement. Reloads the current browser page using Puppeteer and returns a success message with the current URL.
    case "reload":
  await page.reload({ waitUntil: "domcontentloaded" });
  const currentUrl = page.url();
  return {
    content: [
      {
        type: "text",
        text: `Reloaded page: ${currentUrl}`,
      },
    ],
    isError: false,
  };
  • src/index.ts:35-39 (schema)
    Input schema definition for the 'reload' tool, specifying an empty object with no required properties.
    inputSchema: {
  type: "object",
  properties: {},
  required: [],
},
  • src/index.ts:32-40 (registration)
    Registration of the 'reload' tool in the TOOLS array, which is served via the MCP ListTools handler.
    {
  name: "reload",
  description: "Reload the current page",
  inputSchema: {
    type: "object",
    properties: {},
    required: [],
  },
},

Tool Definition Quality

B3.2/5.0
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. 'Reload' implies a page refresh, but it doesn't specify whether this preserves session data, handles JavaScript execution, or has side effects like triggering page events. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 waste—'Reload the current page' directly conveys the core action without unnecessary elaboration. It's appropriately sized and front-loaded 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?

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It states what the tool does but fails to address behavioral aspects like side effects or usage context, which are important for a browser interaction tool. A score of 3 reflects this basic sufficiency with clear gaps.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no required inputs by not mentioning any. A baseline of 4 is appropriate for zero-parameter tools.

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 'Reload the current page' clearly states the action (reload) and target (current page) with a specific verb+resource. However, it doesn't differentiate from potential sibling tools like 'navigate' or 'reset_browser_data' that might have overlapping functionality, preventing a perfect score.

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 'navigate' for URL changes or 'reset_browser_data' for clearing cache. It lacks explicit when/when-not instructions or named alternatives, offering only a basic action statement.

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/noisysocks/autoconsent-mcp'

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