Skip to main content
Glama
Sign In

The Daily Workflow — AI Tools & Free Alternatives

by com.thedailyworkflow
OverviewDiscussionsAdmin

get_my_saved_tools

Read-onlyIdempotent

Return the saved AI tools ("My Workflow" stack) of the user who owns the given personal API key from thedailyworkflow.com.

The user can generate the key on https://thedailyworkflow.com/my-workflow
(section "Personal API key"). Ask the user for the key if you do not have it.

Returns:
    Dict with `count` and `results`: each result has name, url (official
    site), page_url (catalog page), pricing and health (liveness status:
    alive / protected / slow / dead / unknown — re-checked every 4 hours).

Use this when the user asks about "my tools", "my stack", "what did I save"
in the context of TheDailyWorkflow.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "get_my_saved_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesPersonal API key of the TheDailyWorkflow account, generated at https://thedailyworkflow.com/my-workflow (section "Personal API key"). It is sent as a Bearer token and selects whose saved tools are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds what they cannot: the Bearer-token auth requirement, where the key is generated, and the 4-hour re-check cadence for health status with its enumerated states. This is exactly the value-add expected beyond structured 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-loaded purpose followed by auth setup and a structured Returns block; each section is useful. Minor redundancy between the description's key guidance and the schema's api_key description, but no filler.

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?

With no output schema, the description correctly documents the return shape (count, results with name/url/page_url/pricing/health) and explains health state semantics. Auth handling and usage triggers are covered, leaving nothing an agent needs before calling.

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 coverage is 100%, so the api_key semantics (Bearer token selecting whose tools are returned) are already documented in the schema. The description restates the key-generation location without adding new syntax, format, or validation details, so the baseline of 3 applies.

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+resource ("Return the saved AI tools") scoped to the authenticated user via the personal API key, and names the product concept ("My Workflow" stack) so it is clearly distinct from catalog-wide siblings like search_ai_tools or catalog_stats.

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?

Gives explicit trigger phrases ("my tools", "my stack", "what did I save") scoped to TheDailyWorkflow context, plus operational guidance to "Ask the user for the key if you do not have it." It stops short of naming a sibling alternative (e.g. get_my_stack_health) for related health questions.

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

All The Daily Workflow — AI Tools & Free Alternatives toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources