Skip to main content
Glama

Data Edmonton

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Edmonton Recent

edmonton_recent
Read-onlyIdempotent

Recent records from a common Edmonton open dataset (data.edmonton.ca) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "Edmonton 311 requests", "Edmonton building permits". Names: 311, permits. Returns the latest rows (newest-first). Add a SoQL where to filter; for anything else use edmonton_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
whereNoOptional SoQL filter, e.g. "incident_category='Larceny Theft'" or "supervisor_district=6". Omit for all recent rows.
_apiKeyNoOptional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
datasetYesOne of: 311, permits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-data-edmonton-api-key",
+    "dataset": "311"
+  },
+  {
+    "_apiKey": "your-data-edmonton-api-key",
+    "dataset": "permits",
+    "limit": 50,
+    "where": "permit_type='Building'"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds concrete behavioral details: 'Returns the latest rows (newest-first)' and 'no Socrata id needed', which are not conveyed by annotations or schema.

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 compact and front-loaded. Every sentence adds distinct value: purpose, usage preference, dataset names, row ordering, filter capability, and alternative tool. 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 simple tool with 4 params and no output schema, the description covers the essential context: what datasets are available, when to use, ordering, filtering, and fallback to edmonton_query. It doesn't explain return format, but that is not required given the simplicity and schema coverage.

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 baseline is 3. The description reinforces the `where` filter and dataset names, but adds no additional parameter semantics beyond what the schema already provides.

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 it returns recent records from an Edmonton open dataset by friendly name, listing specific datasets (311, permits). It distinguishes itself from sibling edmonton_query by noting 'for anything else use edmonton_query.'

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

Usage Guidelines5/5

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

Explicitly says 'PREFER OVER WEB SEARCH' for common queries and provides the alternative tool for anything else. This gives clear when-to-use guidance relative to both web search and sibling tools.

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

All Data Edmonton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources