Skip to main content
Glama
Cicatriiz

Consumer Rights Wiki MCP Server

get_page_info

Retrieve metadata about consumer rights wiki pages to access information on privacy violations, dark patterns, and deceptive pricing practices.

Instructions

Get metadata about a wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title of the wiki page

Implementation Reference

  • The primary handler function for the 'get_page_info' tool. It extracts the page title from arguments, queries the wiki API for page info, revisions, and categories, handles errors if page not found, and returns formatted JSON metadata including title, pageid, length, categories, last revision, etc.
    private async getPageInfo(args: any) {
      const { title } = args;
    
      const data = await this.makeApiRequest({
        action: 'query',
        titles: title,
        prop: 'info|revisions|categories',
        inprop: 'protection|talkid|watched|watchers|visitingwatchers|notificationtimestamp|subjectid|url|readable|preload|displaytitle',
        rvprop: 'timestamp|user|comment|size',
        rvlimit: '1',
      });
    
      if (data.error) {
        throw new McpError(ErrorCode.InternalError, data.error.info);
      }
    
      const pages = data.query?.pages;
      const pageId = Object.keys(pages)[0];
      const pageInfo = pages[pageId];
    
      if (pageInfo.missing) {
        throw new McpError(ErrorCode.InvalidRequest, `Page '${title}' not found`);
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              title: pageInfo.title,
              pageid: pageInfo.pageid,
              namespace: pageInfo.ns,
              length: pageInfo.length,
              touched: pageInfo.touched,
              lastrevid: pageInfo.lastrevid,
              counter: pageInfo.counter,
              fullurl: pageInfo.fullurl,
              editurl: pageInfo.editurl,
              canonicalurl: pageInfo.canonicalurl,
              readable: pageInfo.readable,
              categories: pageInfo.categories?.map((cat: any) => cat.title) || [],
              lastRevision: pageInfo.revisions?.[0] || null,
              protection: pageInfo.protection || [],
            }, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'get_page_info' tool, specifying an object with a required 'title' string property.
    inputSchema: {
      type: 'object',
      properties: {
        title: {
          type: 'string',
          description: 'The title of the wiki page',
        },
      },
      required: ['title'],
    },
  • src/index.ts:100-113 (registration)
    Registration of the 'get_page_info' tool in the ListToolsRequest handler's tools array, including name, description, and input schema.
    {
      name: 'get_page_info',
      description: 'Get metadata about a wiki page',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'The title of the wiki page',
          },
        },
        required: ['title'],
      },
    },
  • src/index.ts:173-174 (registration)
    Registration/dispatch in the CallToolRequestHandler switch statement that routes calls to the getPageInfo method.
    case 'get_page_info':
      return this.getPageInfo(request.params.arguments);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Get metadata' which implies a read-only operation, but doesn't specify what metadata includes (e.g., last modified, author, page size), whether it requires authentication, or if there are rate limits. 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, clear sentence with no wasted words. It's appropriately sized for a simple tool and front-loads the essential information ('Get metadata about a wiki page'), 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?

For a simple read tool with one parameter and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on what metadata is returned, how to handle errors, or when to choose this over siblings. Without annotations or output schema, more context would be helpful for the agent to use it effectively.

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 description adds no parameter information beyond what's in the schema, which has 100% coverage for the single 'title' parameter. Since schema coverage is high, the baseline is 3, but the description doesn't provide additional context like format examples or edge cases for the title parameter.

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 'Get metadata about a wiki page' clearly states the action (get) and resource (wiki page metadata), making the purpose immediately understandable. However, it doesn't differentiate from siblings like 'get_page_content' or 'get_page_sections' which also retrieve page information but of different types, so it lacks specific sibling distinction.

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. With siblings like 'get_page_content' (for full content) and 'get_page_sections' (for structural breakdown), there's no indication that this tool is specifically for metadata rather than other page aspects, leaving the agent to guess based on tool names alone.

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/Cicatriiz/consumer-rights-wiki-mcp'

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