Skip to main content
Glama

AgentDeals

by io.github.robhunter

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: 7 days ago.
vendorNoFilter to one vendor (case-insensitive)
vendorsNoComma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section.
categoriesNoComma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Case-insensitive partial match.
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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. 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"
+]
  3. 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"
+]
  4. 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."
  5. 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"
+}
  6. 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"
+]
  7. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  8. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false. The description adds useful context about what kinds of changes are covered, but does not disclose operational behavior such as result format, pagination, or update latency. It is consistent with the annotations and adds moderate context, but not significantly beyond them.

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 three sentences with the core purpose front-loaded, followed by concrete use cases and example queries. Every sentence earns its place, and there is no filler or redundant restatement of the tool name.

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?

For a read-only tool with 8 parameters and no output schema, the description explains when to call it and what topics it covers, and the schema handles parameter details. It does not explicitly describe the shape or structure of the returned data, which would make it fully complete without an output schema.

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 already documents all 8 parameters. The description does not add parameter-level meaning beyond what is in the schema, so it meets the baseline but does not elevate it.

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?

The description uses a specific verb and resource: 'Track recent pricing changes across developer tools' and lists concrete examples ('free tiers removed, limits cut, improved'). This clearly distinguishes it from siblings like compare_vendors or search_deals, none of which cover pricing-change monitoring.

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 explicitly says when to use the tool ('stay current on infrastructure pricing', 'verify that a recommended service still has its free tier') and provides direct user-query triggers. It does not explicitly mention when not to use it or name alternatives, so it misses the full exclusionary guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation3/5

The discovery-oriented tools—search_deals, compare_vendors, track_changes, and plan_stack—overlap in purpose and can be confused, especially for queries like 'What's cheaper than Vercel?' or 'Are free tiers being removed?'. The referral and account tools are clearly distinct, but the overlapping query surface lowers the overall disambiguation quality.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern such as check_balance, submit_referral_code, and request_payout. Two tools deviate: 'leaderboard' is a bare noun and 'my_referral_codes' uses a possessive prefix, creating minor inconsistency.

Tool Count5/5

Twelve tools is well within the ideal range and each tool covers a meaningful part of the AgentDeals domain: deal discovery, referral management, agent registration, payouts, and social routing. None of the tools feel redundant or extraneous.

Completeness4/5

The tool surface covers the main agent lifecycle well: registration, referral code submission and retrieval, balance checking, payouts, and friend management. Minor gaps exist—there is no way to update or remove a submitted referral code, and the payout address must be configured via an out-of-band API endpoint.

Resources