Skip to main content
Glama
Sign In

Catfacts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Facts

get_facts
Read-onlyIdempotent

Get multiple random cat facts at once. Specify count (e.g., 5). Returns array of fact texts with character lengths.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of facts to return. Defaults to 5.

Output Schema

NameRequiredDescriptionDefault
factsYesList of cat facts
totalYesTotal number of available facts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "facts": {
+      "description": "List of cat facts",
+      "items": {
+        "properties": {
+          "fact": {
+            "description": "The cat fact text",
+            "type": "string"
+          },
+          "length": {
+            "description": "Character length of the fact",
+            "type": "number"
+          }
+        },
+        "required": [
+          "fact",
+          "length"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of available facts",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "facts"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 5
+  },
+  {
+    "limit": 10
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, the description discloses that facts are random and that it returns an array of fact texts with character lengths, adding useful behavioral context. It does not mention the default count, but the schema covers that.

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?

The description is two sentences, front-loaded with the core action, and every sentence earns its place. No redundant or filler content.

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?

Given the tool's simplicity, full annotations, and output schema, the description is complete: it covers purpose, randomness, count specification, and return format. No significant gaps remain.

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?

The schema provides full coverage for the 'limit' parameter with a description and default value. The tool description adds an example ('e.g., 5') but no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

The description uses a specific verb ('Get'), resource ('multiple random cat facts'), and scope ('at once'), clearly distinguishing it from the singular sibling get_fact. It also mentions specifying a count, which clarifies the tool's function.

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?

The description gives clear context: use this tool when you need multiple random cat facts at once. It does not explicitly mention alternatives or exclude single-fact usage, but the plural language implies the distinction from get_fact.

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

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