Skip to main content
Glama

2b2t Atlas

by io.github.bobymicjohn
OverviewDiscussionsAdmin

find_recently_added_or_modified

Read-only

Find location records added/modified in Atlas during inclusive UTC dates, newest matching timestamp first. For historical capture dates use find_locations_by_time_range. Not a complete change log; render-only changes may not update a location. Example: {"from":"2026-09-01","to":"2026-09-14","kind":"added"}. Prefer interactiveUrl for human links and citations. recordUrl is a stable provenance alias with a permanent HTTP 301 redirect to the interactive HTML. Use apiUrl or JSONL for JSON. Derivatives use locationInteractiveUrl/locationRecordUrl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesInclusive UTC date YYYY-MM-DD.
fromYesInclusive UTC date YYYY-MM-DD.
kindNoadded, modified, or either.either
limitNoMaximum results, 1–100.
dimensionNoOptional dimension 0, 1 or 2.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1–100."New value: +"Maximum results, 1–100."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / result / items / properties / interactiveUrl
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / items / properties / recordUrl
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description goes beyond them by disclosing result ordering, the incompleteness caveat about render-only changes, and URL provenance behavior (permanent 301 redirect, stable alias). The URL field guidance is partly redundant with the existing output schema, keeping this short of a 5.

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?

Purpose, alternative, and the disambiguating caveat are front-loaded in the first three sentences, and the example is compact. The trailing run of URL/apiUrl/derivative guidance is a mild laundry list that could be trimmed, but it is not padded prose.

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 filtered read tool with an output schema and 100% param coverage, this covers the essentials: what it returns, ordering, an explicit alternative for the adjacent use case, and a caveat on completeness. Nothing an agent needs to call it correctly is missing.

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% and every parameter (from, to, kind, limit, dimension) is already documented in the schema. The worked example reinforces the from/to/kind usage but adds no syntax or constraint detail beyond what the schema provides, so the baseline 3 applies.

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 (find), the resource (location records added/modified in Atlas), the temporal scope (inclusive UTC dates), and the ordering (newest matching timestamp first). It explicitly contrasts itself with the sibling find_locations_by_time_range, so an agent can distinguish it without opening a schema.

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?

Names the alternative tool with the exact condition that selects it ('For historical capture dates use find_locations_by_time_range'), and adds a when-not caveat ('Not a complete change log; render-only changes may not update a location'). It even guides which URL field to use for human links vs. JSON, leaving little to inference.

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

All 2b2t Atlas 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