Skip to main content
Glama
Sign In
pxweb-mcp

pxweb-mcp

by jarib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_recent_tables

Find newly published statistics by listing tables updated within a specified number of days. Specify days to look back to discover recent data releases.

Instructions

List tables updated in the past N days.

Use this to find newly published statistics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": "<days>"
    },
    "name": "list_recent_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesNumber of days to look back.
languageNoLanguage - 'no' for Norwegian (default), 'en' for English.no

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and clearly states the operation (listing), the selection criterion (tables updated within N days), and the intended purpose. It is non-destructive and transparent, though it does not describe the return format or any limits.

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?

Two short sentences that front-load the action and temporal scope, followed by the intended use case. There is no redundant or filler content.

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

Completeness4/5

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

For a tool with only two parameters and no output schema, the description is sufficient to invoke it correctly. The schema covers parameter details and the description adds the use case, though naming sibling alternatives would improve completeness.

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%, so the schema fully documents both parameters. The description references 'N days' but adds little meaning beyond what the schema already provides, so baseline 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 uses a specific verb ('List') and resource ('tables') with a clear temporal filter ('updated in the past N days'). It clearly communicates the tool's scope, though it does not explicitly differentiate it from sibling tools like search_tables.

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

Usage Guidelines4/5

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

The sentence 'Use this to find newly published statistics' provides an explicit intended use case. It does not mention exclusions or alternatives, but the context is clear enough for a simple list tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools