Skip to main content
Glama
Sign In

Opendatasoft

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Instance Info

instance_info
Read-onlyIdempotent

Fetch catalog-level metadata for an Opendatasoft portal instance (total dataset count, themes, languages); defaults to public.opendatasoft.com.

Input Schema

NameRequiredDescriptionDefault
instanceNo

Output Schema

NameRequiredDescriptionDefault
linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / datasets_count
      Removed value: -{
-  "description": "Total number of datasets",
-  "type": "number"
-}
    • addedOutput schema / properties / links
      Added value: +{
+  "items": {
+    "properties": {
+      "href": {
+        "type": "string"
+      },
+      "rel": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / name
      Removed value: -{
-  "description": "Instance name",
-  "type": "string"
-}
    • removedOutput schema / properties / records_count
      Removed value: -{
-  "description": "Total number of records across all datasets",
-  "type": "number"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "instance": "public.opendatasoft.com"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Instance metadata and catalog information",
+  "properties": {
+    "datasets_count": {
+      "description": "Total number of datasets",
+      "type": "number"
+    },
+    "name": {
+      "description": "Instance name",
+      "type": "string"
+    },
+    "records_count": {
+      "description": "Total number of records across all datasets",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the burden is lower. The description adds the default-instance behavior and hints at the returned aggregate fields, but says nothing about pagination, rate limits, or error behavior on unknown instances.

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?

One sentence with the verb and resource front-loaded, parenthetical detail on the return payload, and the default tucked at the end. No filler or repetition.

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?

An output schema exists, so return values need not be documented, though the description helpfully summarizes them anyway. For a single-optional-parameter read tool, nothing essential is missing; only edge-case behavior for invalid instances is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single 'instance' parameter has no description in the schema — but the description compensates by naming the default value (public.opendatasoft.com) and the example reinforces the expected host-style format. That is meaningful semantics beyond the raw schema.

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?

States a specific verb and resource ('Fetch catalog-level metadata for an Opendatasoft portal instance') and enumerates what the metadata contains (dataset count, themes, languages). This clearly separates it from dataset-level siblings like datasets, records, and facets.

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

Usage Guidelines3/5

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

The default target ('public.opendatasoft.com') is supplied, which is useful invocation context, but there is no explicit when-to-use or when-not guidance relative to alternatives, and no statement of prerequisites. Usage is implied rather than prescribed.

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

All Opendatasoft 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