Skip to main content
Glama
Sign In

Loafy: Sourdough Bread Baking

by ai.loafy
OverviewDiscussionsAdmin

My Loafy starters

list_my_starters
Read-onlyIdempotent

The baker's own sourdough starters in Loafy: name, birthday and age, notes and story, how many bakes each went into and when last, each with its id and a link. A new starter is add_starter, a change to one is update_starter. Needs the baker's Loafy account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_starters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlNoThe same answer, recipe or entry on loafy.ai.
noteNoA remark on the whole result, such as why nothing was found.
toolNoThe tool that answered.
inputNoThe arguments as the tool used them, after any correction.
notesNoWhat was corrected or left out, such as a value outside its range.
startersNoBy name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "The baker's starters.",
+  "properties": {
+    "input": {
+      "description": "The arguments as the tool used them, after any correction.",
+      "properties": {},
+      "type": "object"
+    },
+    "note": {
+      "description": "A remark on the whole result, such as why nothing was found.",
+      "type": "string"
+    },
+    "notes": {
+      "description": "What was corrected or left out, such as a value outside its range.",
+      "items": {
+        "description": "A correction or remark.",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "starters": {
+      "description": "By name.",
+      "items": {
+        "description": "One of the baker's starters.",
+        "properties": {
+          "age_days": {
+            "description": "Its age in days.",
+            "type": "integer"
+          },
+          "bakes": {
+            "description": "How many bakes it went into.",
+            "type": "integer"
+          },
+          "birthday": {
+            "description": "The day it was started, YYYY-MM-DD.",
+            "type": "string"
+          },
+          "id": {
+            "description": "The starter's id, which update_starter takes.",
+            "type": "string"
+          },
+          "last_baked_on": {
+            "description": "Its last bake, YYYY-MM-DD.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Its name.",
+            "type": "string"
+          },
+          "notes": {
+            "description": "Notes on it.",
+            "type": "string"
+          },
+          "story": {
+            "description": "Its story.",
+            "type": "string"
+          },
+          "url": {
+            "description": "The starter on loafy.ai.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "description": "The tool that answered.",
+      "type": "string"
+    },
+    "url": {
+      "description": "The same answer, recipe or entry on loafy.ai.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: the tool is scoped to the baker's own starters (not community/shared ones) and it discloses the auth prerequisite, 'Needs the baker's Loafy account.' It adds no rate-limit or freshness/pagination detail, but that is minor here.

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 with the resource and its contents, then alternatives, then the auth note. The field enumeration is slightly long but each item is substantive information for selection, no filler sentences.

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?

An output schema exists, so return values need not be explained, and the annotations fully cover the safety profile. Combined with the stated auth requirement and the sibling routing, an agent has everything needed to select and call this correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema coverage is moot. Baseline for a 0-param tool 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 (the baker's own sourdough starters) and enumerates exactly what each entry contains: name, birthday/age, notes/story, bake counts, timestamps, id and link. It is immediately distinguishable from sibling readers like list_my_bakes or list_my_containers.

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 routes the agent to the mutation siblings: 'A new starter is add_starter, a change to one is update_starter.' This makes the read-vs-write boundary clear, though it never states an explicit 'use this when you need to view starters' condition or any exclusion.

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

All Loafy: Sourdough Bread Baking 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