SOS.city public record

Buy credits or a city data pack

buy

Starts a one-time purchase and returns a Stripe Checkout link for the person who pays, plus a status_url to poll. product: credits_1k ($10), credits_10k ($79), city_pack ($29, needs place) or compliance_list ($99, one whole compliance list as CSV, needs list). The person must agree to the data-use terms (no screening or profiling people): pass agree_data_use=true only after they have.

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": {
      "product": "<product>",
      "email": "<email>",
      "agree_data_use": "<agree_data_use>"
    },
    "name": "buy"
  }
}

Input Schema

Name	Required	Description
`list`	No	For compliance_list: a list id from list_compliance, e.g. sb721-cited.
`email`	Yes	Email of the person paying. Receipts and the account go there.
`place`	No	For city_pack: a place id, e.g. us-ca-los-angeles.
`product`	Yes
`personhood`	No	Optional 5arz proof-of-personhood credential (pop_jwt) showing a verified human stands behind this agent. Recorded with the order.
`agree_data_use`	Yes	True once the person accepts: no tenant, employment, credit or insurance screening, and no locating or profiling anyone.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / list

Added value: +{
+  "description": "For compliance_list: a list id from list_compliance, e.g. sb721-cited.",
+  "type": "string"
+}

changedInput schema / properties / product / enum

Previous value: -[
-  "credits_1k",
-  "credits_10k",
-  "city_pack"
-]New value: +[
+  "credits_1k",
+  "credits_10k",
+  "city_pack",
+  "compliance_list"
+]

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent mutation; the description adds genuine behavior beyond them: the purchase is asynchronous (poll status_url) and the returned link is for the payer in the email field. It omits whether repeated calls spawn duplicate checkout sessions, which matters given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and return values in the first sentence, then enumerates products, then the terms gate. Dense but every clause carries information; a slightly tighter product list would improve scannability.

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?

With no output schema, the description still explains what comes back (checkout link, status_url) and the payment/consent flow, which is the key risk area. Remaining gaps like link expiry or duplicate-session behavior are modest for a single-purpose purchase tool.

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 coverage is 83%, so the schema already documents most parameters. The description adds real value by mapping product to price and to its dependent parameter (place for city_pack, list for compliance_list) and by explaining the timing of agree_data_use, but the pricing/enum mapping is the main addition.

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 ('Starts a one-time purchase') and names the concrete artifacts returned ('a Stripe Checkout link ... plus a status_url to poll'). This distinguishes it clearly from browsing-oriented siblings like get_store or get_city_pack.

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?

Gives per-product conditions (city_pack needs place, compliance_list needs list) and gates the call on the person having agreed to the data-use terms, which tells the agent the prerequisite for invoking. It stops short of naming an alternative sibling to browse products first (e.g., get_store), so no explicit 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 SOS.city public record tools Inspect

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

Need Help?