Skip to main content
Glama

Server Details

Agent-payable open-loop tracker for refunds, returns, and asks with TRACE receipts.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: retrieve one loop by ID, list loops by due date, and register a new loop. There is no meaningful overlap in purpose or trigger conditions.

Naming Consistency4/5

All names use snake_case with a leading verb and are readable as a set. The minor inconsistency is that list_due does not name the resource (loops) while get_loop and register_loop do.

Tool Count4/5

Three tools is a small but coherent surface for a focused loop-tracking desk. It is slightly thin, but each tool has a clear place and it does not feel over-scoped.

Completeness2/5

The set supports fetching, due-listing, and registering loops, but it lacks core lifecycle operations such as closing, resolving, updating, or reassigning loops. Agents can create and inspect loops but will hit a dead end when they need to act on them.

Available Tools

3 tools
get_loopBInspect

Fetch one loop by id for the calling API key.

Inputs: id (required).

list_dueBInspect

List open loops due on or before before (ISO datetime).

Inputs: before.

register_loopBInspect

Register an open loop (refund, return, price_adjustment, delivery, unanswered, other). Returns TRACE receipt. Needs an API key: keyless calls are read-only (get_loop, list_due).

Inputs: kind (required), due_at (required), counterparty (required), notes, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources