VerveContext
VerveContextDocumentation
Ctrl+K

State Boundary Grounding DataState Boundary Grounding Data

OnlineCredit Usage:5 per callTool:StateBoundaryGroundingData

The tool

Ground agents in verifiable US state boundary geometry so mapping and geospatial answers rest on real census GeoJSON, not approximation.

Once your client is connected to the VerveContext MCP server, this appears in its tool list as StateBoundaryGroundingData. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "StateBoundaryGroundingData",
  "arguments": {
    "state": "CA"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about CA in the terms this source covers is enough for it to reach for StateBoundaryGroundingData on its own.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervecontext.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
stateRequiredstringCAThe 2 Letter State Code (e.g., CA)

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "type": "FeatureCollection",
    "features": [
      {
        "type": "Feature",
        "geometry": {
          "coordinates": [
            [
              [
                [
                  -124.136560999568,
                  41.4644520001748
                ],
                [
                  -124.144127999686,
                  41.4868809999681
                ],
                [
                  -124.151304999817,
                  41.4998419999228
                ],
                [
                  -124.151821000201,
                  41.5082140000472
                ],
                [
                  -124.157942999997,
                  41.5189619997364
                ],
                [
                  -124.160111000392,
                  41.5293859999524
                ],
                [
                  -124.160492999984,
                  41.5434089997226
                ],
                [
                  -124.172273999795,
                  41.5509789998463
                ],
                [
                  -124.179960999564,
                  41.5583250000071
                ],
                [
                  -124.18499000029,
                  41.5657689998144
                ],
                [
                  -124.188336000144,
                  41.5739960002055
                ],
                [
                  -124.187126999824,
                  41.5889699998552
                ],

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
typestringFeatureCollectionGeoJSON type indicator for feature collection
featuresarray[1]list of rowsArray of GeoJSON feature objects representing state boundaries
└ features.0.typestringFeatureGeoJSON type indicator for individual feature object
└ features.0.geometryPremiumobject{…}GeoJSON geometry object with coordinates and type
└ features.0.geometry.coordinatesPremiumarraylist of listsNested array of coordinate arrays defining boundary polygons
└ features.0.geometry.typePremiumstringMultiPolygonGeometry type (e.g., MultiPolygon, Polygon)
└ features.0.propertiesobject{…}Object containing state boundary properties and metadata
└ features.0.properties.gidPremiumnumber48Global identifier for the state boundary
└ features.0.properties.arealandPremiumstring-222385618Land area measurement value
└ features.0.properties.divisionPremiumnumber9Census division code for state
└ features.0.properties.intptlatPremiumnumber37.1551773Interior point latitude for state centroid
└ features.0.properties.namestringCaliforniaState name (e.g., California)
└ features.0.properties.objectidPremiumnumber14Object identifier for the state feature
└ features.0.properties.areawaterPremiumstring-1011556647Water area measurement value
└ features.0.properties.intptlonPremiumnumber-119.5434183Interior point longitude for state centroid
└ features.0.properties.oidPremiumstring239405626Unique object identifier string
└ features.0.properties.funcstatPremiumstringAFunctional status code for the state
└ features.0.properties.centlonPremiumnumber-119.527746Longitude of geographic center point
└ features.0.properties.stusabstringCATwo-letter state abbreviation (e.g., CA)
└ features.0.properties.statestring06State FIPS code numeric identifier
└ features.0.properties.statensPremiumstring01779778State ANSI/FIPS numeric identifier
└ features.0.properties.centlatPremiumnumber37.1547352Latitude of geographic center point
└ features.0.properties.basenamestringCaliforniaBase name of the state geography
└ features.0.properties.mtfccPremiumstringG4000MAF/TIGER feature class code
└ features.0.properties.regionPremiumnumber4Census region code for state
└ features.0.properties.lsadcPremiumstring00Legal/statistical area description code
└ features.0.properties.geoidstring06Geographic identifier for state
└ features.0.properties.geo_point_2dPremiumobject{…}Two-dimensional geographic point object
└ features.0.properties.geo_point_2d.lonPremiumnumber-119.663749804Longitude coordinate of point
└ features.0.properties.geo_point_2d.latPremiumnumber37.2153570137Latitude coordinate of point

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at type: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This source isn't part of VerveContext. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use State Boundary Grounding Data

Set up State Boundary Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Frequently asked questions

Do I have to tell the agent to use StateBoundaryGroundingData?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

5 credits each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Browse all sources

The full catalog for this door

Connect a client

Claude, Cursor, VS Code and the rest

Plans & credits

What a call costs and how usage resets

Was this page helpful?