WellFred — Services in Costa Rica

Show WellFred offering cards

wellfred_render_services

Show read-only visual cards for selected service IDs and/or class IDs returned by WellFred. Choose the IDs in the order to present them. The server reloads public Costa Rica catalog facts; unavailable IDs are reported, not replaced. No search, availability check or booking. Prices, photos and website URLs cannot be supplied by the model. Set optional presentationLocale to es or en according to the conversation or explicit user choice; catalog text is not translated.

Input Schema

Name	Required	Description
`classIds`	No
`serviceIds`	No
`presentationLocale`	No	UI language chosen from the conversation or explicit user preference; does not change catalog facts.

Output Schema

Name	Required	Description	Default
`success`	No
`httpStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / allOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 12
+          },
+          "serviceIds": {
+            "maxItems": 0
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 11
+          },
+          "serviceIds": {
+            "maxItems": 1
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 10
+          },
+          "serviceIds": {
+            "maxItems": 2
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 9
+          },
+          "serviceIds": {
+            "maxItems": 3
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 8
+          },
+          "serviceIds": {
+            "maxItems": 4
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 7
+          },
+          "serviceIds": {
+            "maxItems": 5
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 6
+          },
+          "serviceIds": {
+            "maxItems": 6
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 5
+          },
+          "serviceIds": {
+            "maxItems": 7
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 4
+          },
+          "serviceIds": {
+            "maxItems": 8
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 3
+          },
+          "serviceIds": {
+            "maxItems": 9
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 2
+          },
+          "serviceIds": {
+            "maxItems": 10
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 1
+          },
+          "serviceIds": {
+            "maxItems": 11
+          }
+        }
+      },
+      {
+        "properties": {
+          "classIds": {
+            "maxItems": 0
+          },
+          "serviceIds": {
+            "maxItems": 12
+          }
+        }
+      }
+    ]
+  }
+]

First observedOct 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Discloses behavior well beyond the annotations: the server reloads public Costa Rica catalog facts, unavailable IDs are reported rather than substituted, and the model cannot inject prices, photos or website URLs. The 'read-only' phrasing refers to the cards being display-only rather than to tool side effects, and the accompanying note that the server reloads catalog facts keeps this consistent with readOnlyHint=false and destructiveHint=false.

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?

Four sentences, front-loaded with the action, then constraints, then the locale caveat; nothing is wasted. It is dense to the point of being slightly run-on, but every clause carries operational meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and the description covers the mutation/reload behavior, failure reporting and locale semantics. The one missing piece an agent needs before calling is the combined 12-item cap and the UUID origin of each ID array.

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?

With schema description coverage at 33%, the description must carry the load for classIds and serviceIds, and it partially does: it says to choose IDs in the order to present them and that they come from WellFred. It omits the key structural constraint that classIds plus serviceIds together cap at 12 items (encoded only in the anyOf), and does not say which sibling search tool produces which ID type.

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 and resource — show read-only visual cards for service IDs and/or class IDs returned by WellFred — and immediately names what it is not (no search, availability check or booking), which separates it from wellfred_search_services, wellfred_offering_detail and wellfred_service_availability without opening a schema.

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 a clear precondition (IDs already returned by WellFred) and explicit exclusions that function as when-not-to-use guidance. It stops short of naming the sibling tools an agent should pick instead for search or booking, so it is strong but not fully routing.

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

All WellFred — Services in Costa Rica tools Inspect

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

Need Help?