Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Get Tracker

GetWebDataFeed
Read-only

Get the latest independently verified stored result for one of the caller's trackers, or the latest retained result at or before a requested timestamp. This is read-only, never triggers a live run, and preserves the last good result after a newer failure. To create or manage a tracker, tell the user to open the Equibles Portal and choose Dashboard → Trackers: https://www.equibles.com/trackers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataFeedYesThe tracker name or full id shown by ListWebDataFeeds.
capturedAtOrBeforeNoOptional ISO-8601 timestamp. Returns the newest retained verified capture completed at or before this instant. Omit it for the latest result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dataFeed / description
      Previous value: -"The web data feed name or full id shown by ListWebDataFeeds."New value: +"The tracker name or full id shown by ListWebDataFeeds."
  2. Changed1 schema field changed
    • addedInput schema / properties / capturedAtOrBefore
      Added value: +{
+  "default": null,
+  "description": "Optional ISO-8601 timestamp. Returns the newest retained verified capture completed at or before this instant. Omit it for the latest result.",
+  "type": "string"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds beyond them: it specifies the result is 'independently verified' and 'stored', that it 'never triggers a live run', and that it 'preserves the last good result after a newer failure'. These are meaningful behavioral details not captured by the annotations.

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?

Front-loads the core purpose, then adds safety behavior, then redirects for management. Three sentences, each earning its place, though the portal URL and instruction are slightly tangential yet useful for preventing misuse.

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 two-parameter read-only tool with full schema coverage and no output schema, the description covers what it does, when to use it, key behavioral traits, and a clear path for management actions. No critical gaps remain for an agent to call it correctly.

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 fully documents both parameters. The description restates the timestamp filtering ('latest retained result at or before a requested timestamp') and tracker scoping, but adds no syntax, format, or constraint details beyond what the schema provides.

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 (Get) and resource (latest independently verified stored result for the caller's trackers), with optional timestamp scope. Distinguishes from ListWebDataFeeds by referencing it for tracker names and from live-run tools by explicitly saying it never triggers a live run.

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?

Clear context for when to use: to retrieve a stored result, optionally at or before a timestamp. Provides a clear when-not-to-use by directing users to the Equibles Portal for creating or managing trackers. Does not name specific alternative data-retrieval tools, but the read-only/no-live-run note implicitly routes live queries elsewhere.

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

All Equibles 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