Skip to main content
Glama
Sign In

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

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

Output 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 to 100."
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1–100."New value: +"Maximum results, 1–100."
  3. 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"
+  ]
+}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read-only profile, and the description adds real behavioral context: result ordering (newest matching timestamp first), the incompleteness of change capture, and the semantics of each returned URL type including the permanent 301 redirect behind recordUrl. This goes well beyond what annotations provide.

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?

Scope, alternative and caveats are front-loaded in the first two sentences, which is exactly the right ordering. The trailing four sentences on URL field selection are somewhat sprawling and partly duplicate what the output schema can convey.

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?

Covers everything an agent needs for a filtered-list tool: date scope, ordering, mutation caveats, the exclusion to a sibling, and guidance on which returned URL field to cite. With an output schema present, further return-value detail is unnecessary.

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 100%, so from/to format, kind values, limit bounds and dimension are already documented. The inline example reinforces the date format and shows a concrete kind value, but it doesn't add new semantics for limit or dimension, 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+resource+scope: location records added/modified in Atlas within inclusive UTC dates, ordered newest-first. It explicitly distinguishes itself from the sibling find_locations_by_time_range by assigning historical capture dates to that tool.

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?

Gives an explicit routing rule ('For historical capture dates use find_locations_by_time_range') and a scope caveat ('Not a complete change log; render-only changes may not update a location'). An agent knows both when to pick this tool and when its results will be incomplete.

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