Skip to main content
Glama

Openparliament Ca

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds that data is derived from CF analytics-engine, contains no PII, and is cached for 5min-1h depending on window. This provides valuable behavioral context not captured by annotations.

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 concise with three sentences plus a bulleted list of use cases. Every sentence adds value, and the purpose is front-loaded. No unnecessary words.

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

Completeness5/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 optional parameter, no output schema, rich annotations), the description fully covers purpose, use cases, data source, caching behavior, and privacy. Nothing essential is missing.

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 single parameter 'window' is fully described in the schema with enum values and a description. The tool description adds no additional semantic meaning beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'returns' and the resource: 'top tools, top packs, and total call volume' over a defined window. It distinguishes itself from sibling tools by focusing on aggregated trending data from other AI agents, which is unique among the listed tools.

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?

Three explicit use cases are provided (discovering hot data sources, confirming canonical choice, checking alignment). While it does not specify when not to use the tool or name alternative tools, the use cases are clear and context-rich.

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

All Openparliament Ca toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

The tool set mixes two distinct domains: 8 Canadian Parliament tools and 30 Pipeworx data tools. Within each domain, tools are somewhat distinct, but the overall mix creates confusion as agents cannot tell if a tool is for parliament or general data lookup.

Naming Consistency2/5

OpenParliament tools follow a consistent verb_noun pattern (list_*, get_*), but Pipeworx tools use varied conventions (e.g., 'remember', 'discover_tools', 'ask_pipeworx'). The lack of a unified naming scheme across the set reduces predictability.

Tool Count2/5

38 tools is excessive for a Canadian Parliament server. The core parliament tools (8) are well-scoped, but the addition of 30 unrelated Pipeworx tools makes the count bloated and inappropriate for the stated domain.

Completeness1/5

For the Canadian Parliament domain, coverage is adequate but lacks topic search and detailed legislative history. However, the server is dominated by Pipeworx tools, which are out of scope, making the overall surface severely incomplete for the implied purpose.

Resources