Skip to main content
Glama
Cicatriiz

Consumer Rights Wiki MCP Server

get_recent_changes

Retrieve recent edits and updates from the Consumer Rights Wiki to monitor changes in articles about privacy violations, dark patterns, and deceptive pricing practices.

Instructions

Get recent changes to the wiki

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of recent changes to return (default: 10, max: 50)
namespaceNoFilter by namespace (0 = main articles)

Implementation Reference

  • The main handler function for the 'get_recent_changes' tool. It extracts arguments, constructs a MediaWiki API request for recentchanges, fetches data using makeApiRequest, processes the changes into a formatted structure with details like title, timestamp, user, sizes, etc., and returns it as JSON text content.
    private async getRecentChanges(args: any) {
      const { limit = 10, namespace } = args;
    
      const params: Record<string, string> = {
        action: 'query',
        list: 'recentchanges',
        rcprop: 'title|timestamp|user|comment|sizes|flags',
        rclimit: Math.min(limit, 50).toString(),
      };
    
      if (namespace !== undefined) {
        params.rcnamespace = namespace.toString();
      }
    
      const data = await this.makeApiRequest(params);
    
      if (data.error) {
        throw new McpError(ErrorCode.InternalError, data.error.info);
      }
    
      const changes = data.query?.recentchanges || [];
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              recentChanges: changes.map((change: any) => ({
                title: change.title,
                timestamp: change.timestamp,
                user: change.user,
                comment: change.comment,
                oldSize: change.oldlen,
                newSize: change.newlen,
                sizeChange: change.newlen - change.oldlen,
                type: change.type,
                isNew: change.new === '',
                isMinor: change.minor === '',
                isBot: change.bot === '',
                url: `${WIKI_BASE_URL}/${change.title.replace(/ /g, '_')}`,
              })),
            }, null, 2),
          },
        ],
      };
    }
  • The input schema for the 'get_recent_changes' tool, specifying an object with optional 'limit' (number, default 10, max 50) and 'namespace' (number for filtering). No required properties.
    inputSchema: {
      type: 'object',
      properties: {
        limit: {
          type: 'number',
          description: 'Number of recent changes to return (default: 10, max: 50)',
          default: 10,
        },
        namespace: {
          type: 'number',
          description: 'Filter by namespace (0 = main articles)',
        },
      },
    },
  • src/index.ts:114-131 (registration)
    Registration of the 'get_recent_changes' tool in the ListTools response array, providing name, description, and input schema.
    {
      name: 'get_recent_changes',
      description: 'Get recent changes to the wiki',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Number of recent changes to return (default: 10, max: 50)',
            default: 10,
          },
          namespace: {
            type: 'number',
            description: 'Filter by namespace (0 = main articles)',
          },
        },
      },
    },
  • src/index.ts:175-176 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes calls to the getRecentChanges handler method.
    case 'get_recent_changes':
      return this.getRecentChanges(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 the full burden of behavioral disclosure. It states the action but lacks details on permissions, rate limits, output format, pagination, or whether changes are filtered by type (e.g., edits, deletions). For a read operation with zero annotation coverage, this is a significant gap.

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 purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'recent changes' entails (e.g., edit history, timestamps, user info) or the return format, leaving gaps in understanding the tool's behavior and output.

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 input schema has 100% description coverage, with clear documentation for both parameters (limit and namespace), including defaults and examples. The description adds no additional parameter semantics beyond what the schema provides, so 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 ('Get') and resource ('recent changes to the wiki'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'get_page_info' or 'search_wiki' that might also retrieve wiki-related information, 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. With sibling tools like 'get_page_info' and 'search_wiki' available, there's no indication of whether this tool is for chronological updates, specific content types, or other contexts, leaving usage ambiguous.

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