Skip to main content
Glama

AgentDeals

by io.github.robhunter
OverviewDiscussionsAdmin

track_changes

Read-only

Track recent pricing changes across developer tools — which free tiers were removed, which got limits cut, and which improved. Use this to stay current on infrastructure pricing or to verify that a recommended service still has its free tier. Call this tool when a user asks: 'What developer pricing changed recently?', 'Are any free tiers being removed?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoISO date (YYYY-MM-DD). Default: 30 days ago, and only when no other filter is passed — a request carrying type, vendor, vendors, categories or category searches the whole change log unless since says otherwise. The filter compares against each record's date. Where date_meaning is "effective", that is the day the change took effect; where it is "discovered", it is the day we recorded the change, and when it took effect is unknown. Every response states the window it applied under date_window.
vendorNoFilter to one vendor. Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact.
vendorsNoComma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section. Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact.
categoriesNoComma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact.
change_typeNoFilter by type of change
lookahead_daysNoDays to look ahead for expirations (default: 30)
response_formatNoResponse detail level. 'concise': vendor, change_type, date, summary only. 'detailed': full response (default).
include_expiringNoInclude upcoming expirations (default: true)
include_retractedNoRecords we have withdrawn as our own error (standing 'retracted') are left out unless you ask for them. Set true to receive them alongside the rest; they arrive carrying standing 'retracted' and impact 'none'. Either way, retracted_excluded reports how many your query matched and did not receive.
include_index_housekeepingNoRecords of our own index housekeeping (reports 'our_index') are left out unless you ask for them. They say we stopped listing an offer of ours, not that the vendor changed anything, so counting them as vendor activity overstates it. Set true to receive them alongside the rest. Either way, index_housekeeping_excluded reports how many your query matched and did not receive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"ISO date (YYYY-MM-DD). Default: 30 days ago, and only when no other filter is passed — a request carrying type, vendor, vendors, categories or category searches the whole change log unless since says otherwise. The filter compares against each record's date, which is the day the change took effect unless date_source is \"discovered\", in which case it is the day we read the page. Every response states the window it applied under date_window."New value: +"ISO date (YYYY-MM-DD). Default: 30 days ago, and only when no other filter is passed — a request carrying type, vendor, vendors, categories or category searches the whole change log unless since says otherwise. The filter compares against each record's date. Where date_meaning is \"effective\", that is the day the change took effect; where it is \"discovered\", it is the day we recorded the change, and when it took effect is unknown. Every response states the window it applied under date_window."
  2. Changed3 schema fields changed
    • changedInput schema / properties / categories / description
      Previous value: -"Comma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Case-insensitive partial match."New value: +"Comma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact."
    • changedInput schema / properties / vendor / description
      Previous value: -"Filter to one vendor (case-insensitive)"New value: +"Filter to one vendor. Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact."
    • changedInput schema / properties / vendors / description
      Previous value: -"Comma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section."New value: +"Comma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section. Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact."
  3. Changed1 schema field changed
    • addedInput schema / properties / include_index_housekeeping
      Added value: +{
+  "description": "Records of our own index housekeeping (reports 'our_index') are left out unless you ask for them. They say we stopped listing an offer of ours, not that the vendor changed anything, so counting them as vendor activity overstates it. Set true to receive them alongside the rest. Either way, index_housekeeping_excluded reports how many your query matched and did not receive.",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"ISO date (YYYY-MM-DD). Default: 7 days ago."New value: +"ISO date (YYYY-MM-DD). Default: 30 days ago, and only when no other filter is passed — a request carrying type, vendor, vendors, categories or category searches the whole change log unless since says otherwise. The filter compares against each record's date, which is the day the change took effect unless date_source is \"discovered\", in which case it is the day we read the page. Every response states the window it applied under date_window."
  5. Changed1 schema field changed
    • addedInput schema / properties / include_retracted
      Added value: +{
+  "description": "Records we have withdrawn as our own error (standing 'retracted') are left out unless you ask for them. Set true to receive them alongside the rest; they arrive carrying standing 'retracted' and impact 'none'. Either way, retracted_excluded reports how many your query matched and did not receive.",
+  "type": "boolean"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / change_type / enum
      Previous value: -[
-  "free_tier_removed",
-  "limits_reduced",
-  "restriction",
-  "limits_increased",
-  "new_free_tier",
-  "new_tier",
-  "pricing_restructured",
-  "open_source_killed",
-  "pricing_model_change",
-  "startup_program_expanded",
-  "pricing_postponed",
-  "product_deprecated",
-  "rebranded"
-]New value: +[
+  "free_tier_removed",
+  "limits_reduced",
+  "restriction",
+  "limits_increased",
+  "new_free_tier",
+  "new_tier",
+  "pricing_restructured",
+  "open_source_killed",
+  "pricing_model_change",
+  "startup_program_expanded",
+  "pricing_postponed",
+  "product_deprecated",
+  "rebranded",
+  "record_corrected"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / change_type / enum
      Previous value: -[
-  "free_tier_removed",
-  "limits_reduced",
-  "restriction",
-  "limits_increased",
-  "new_free_tier",
-  "new_tier",
-  "pricing_restructured",
-  "open_source_killed",
-  "pricing_model_change",
-  "startup_program_expanded",
-  "pricing_postponed",
-  "product_deprecated"
-]New value: +[
+  "free_tier_removed",
+  "limits_reduced",
+  "restriction",
+  "limits_increased",
+  "new_free_tier",
+  "new_tier",
+  "pricing_restructured",
+  "open_source_killed",
+  "pricing_model_change",
+  "startup_program_expanded",
+  "pricing_postponed",
+  "product_deprecated",
+  "rebranded"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / change_type / enum
      Previous value: -[
-  "free_tier_removed",
-  "limits_reduced",
-  "restriction",
-  "limits_increased",
-  "new_free_tier",
-  "pricing_restructured",
-  "open_source_killed",
-  "pricing_model_change",
-  "startup_program_expanded",
-  "pricing_postponed",
-  "product_deprecated"
-]New value: +[
+  "free_tier_removed",
+  "limits_reduced",
+  "restriction",
+  "limits_increased",
+  "new_free_tier",
+  "new_tier",
+  "pricing_restructured",
+  "open_source_killed",
+  "pricing_model_change",
+  "startup_program_expanded",
+  "pricing_postponed",
+  "product_deprecated"
+]
  9. Changed2 schema fields changed
    • addedInput schema / properties / categories
      Added value: +{
+  "description": "Comma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Case-insensitive partial match.",
+  "type": "string"
+}
    • changedInput schema / properties / vendors / description
      Previous value: -"Comma-separated vendor names to filter (e.g. 'Vercel,Supabase')"New value: +"Comma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section."
  10. Changed1 schema field changed
    • addedInput schema / properties / response_format
      Added value: +{
+  "description": "Response detail level. 'concise': vendor, change_type, date, summary only. 'detailed': full response (default).",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "type": "string"
+}
  11. Changed1 schema field changed
    • changedInput schema / properties / change_type / enum
      Previous value: -[
-  "free_tier_removed",
-  "limits_reduced",
-  "limits_increased",
-  "new_free_tier",
-  "pricing_restructured",
-  "open_source_killed",
-  "pricing_model_change",
-  "startup_program_expanded",
-  "pricing_postponed",
-  "product_deprecated"
-]New value: +[
+  "free_tier_removed",
+  "limits_reduced",
+  "restriction",
+  "limits_increased",
+  "new_free_tier",
+  "pricing_restructured",
+  "open_source_killed",
+  "pricing_model_change",
+  "startup_program_expanded",
+  "pricing_postponed",
+  "product_deprecated"
+]
  12. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  13. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context about what kinds of changes are tracked, but it does not disclose output behavior, window handling, or matching caveats—those live only in the parameter descriptions. This is adequate but not rich behavioral disclosure.

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?

The description is compact: one scope sentence, one purpose sentence, and one trigger sentence. Every sentence earns its place, and the most identifying information is front-loaded.

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?

The tool is complex with 10 parameters, but the schema provides exhaustive parameter documentation, and the description supplies clear use cases and trigger queries. No output schema exists, yet the parameter descriptions document response fields like date_window, name_match, retracted_excluded, and index_housekeeping_excluded. A slightly more explicit distinction from search_deals would make it fully complete.

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 the schema carries the parameter semantics fully. The description's mention of free tiers and limits loosely maps to change_type values but adds no meaning beyond the schema. This meets the baseline of 3 for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb plus resource: 'Track recent pricing changes across developer tools,' and gives concrete examples of change types and exact user queries. It does not explicitly differentiate this tool from siblings like search_deals or compare_vendors, so it falls just short of a 5.

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 gives clear when-to-use guidance: 'Use this to stay current on infrastructure pricing or to verify that a recommended service still has its free tier' and provides trigger example questions. It does not say when not to use the tool or name alternatives, so it misses the explicit exclusion guidance required for a 5.

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

All AgentDeals toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources