Skip to main content
Glama

Thesportsdb

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, no destruction. Description adds behavioral details: listing all keys when omitted, scoping to identifier, and pairing with remember/forget.

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?

Two well-structured sentences. First sentence front-loads core purpose. Each sentence adds value without redundancy.

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 simple tool with full annotations, the description covers purpose, usage, behavior, parameter semantics, and pairing with sibling tools. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, description adds meaning by explaining omission behavior (list all keys) and scoping, going beyond the schema's single parameter description.

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?

Clearly states the verb 'retrieve' and resource 'saved values', distinguishes from siblings by mentioning pairing with remember and forget. Specific usage scenarios are described.

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?

Explicitly tells when to use: 'look up context the agent stored earlier without re-deriving it from scratch'. Does not explicitly list when not to use, but context is clear.

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

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

B3.3/5.0
Disambiguation2/5

The sports tools are distinct, but the majority of the set has heavy overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as query/entry-point tools, with ask_pipeworx and ask_pipeworx_beta explicitly identical. The Polymarket family (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also blurs together.

Naming Consistency2/5

The sports subset follows a clean verb_noun pattern (get_player, list_leagues, search_teams), but the rest mixes several naming schemes: ask_pipeworx*, pipeworx_* prefixed tools, polymarket_* tools, one-word verbs (remember, recall, forget), and compound names like scan_competitor_ai_presence. No single consistent convention governs the set.

Tool Count2/5

42 tools is far too many for a server named Thesportsdb; only 10 tools relate to sports data, while 32 belong to an unrelated Pipeworx data/betting/memory platform. The set feels like two or three servers merged into one, making it heavy and unfocused for any single purpose.

Completeness2/5

For the stated sports domain, the surface is partial: you can get teams, players, league tables, and recent/next fixtures, but there are no player statistics, head-to-head records, venue details, or season history — leaving notable gaps. The Pipeworx half is broad but doesn't belong in a server with this name, so the set as a whole is incomplete for its apparent purpose.

Resources