Skip to main content
Glama
Sign In

Data Sf

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sf Datasets

sf_datasets
Read-onlyIdempotent

Search the San Francisco open-data catalogue (data.sfgov.org, also written data.sf.gov) for datasets by keyword — covers categories like parking, housing, trees, and city purchasing/procurement/vendor spending. Returns dataset names, descriptions, and Socrata resource ids to use with sf_query.

Input Schema

NameRequiredDescriptionDefault
limitNoMax datasets (1-100, default 20).
queryNoKeyword(s), e.g. "parking", "housing", "tree", "purchasing".
offsetNoOffset for paging.
_apiKeyNoOptional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Keyword(s), e.g. \"parking\", \"housing\", \"tree\"."New value: +"Keyword(s), e.g. \"parking\", \"housing\", \"tree\", \"purchasing\"."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-data-sf-api-key",
+    "query": "parking violations"
+  },
+  {
+    "_apiKey": "your-data-sf-api-key",
+    "limit": 30,
+    "query": "housing permits"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, covering the safety profile. The description adds valuable context beyond that: the data source URL, category coverage, and exactly what is returned (names, descriptions, Socrata resource ids). It does not discuss rate limits or auth, but the schema's _apiKey parameter covers that detail.

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 sentences, front-loaded with the core action and resource, then the return values and handoff to sf_query. Every sentence earns its place with zero waste.

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?

For a simple catalogue-search tool with fully documented parameters, examples, and rich annotations, the description is complete. It covers purpose, data source, return format, and sibling relationship; with no output schema, it even explicitly lists return values.

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 all four parameters are already documented in the schema. The description adds no parameter-level semantics beyond what the schema provides, so the baseline of 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?

States a specific verb (Search), resource (San Francisco open-data catalogue), and scope (datasets by keyword). Explicitly names the sibling sf_query and explains the handoff (resource ids to use with sf_query), so an agent can distinguish it from querying tools without inspecting schemas.

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 description implies the discovery-first workflow by saying the returned resource ids are for use with sf_query. This gives clear context, but it does not explicitly state when not to use this tool or name an alternative for already-known resource ids, so it falls short of full when/when-not guidance.

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

All Data Sf 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