list_breedsSearch cat breeds by name or list all available breeds. Returns breed name, country of origin, coat type, and pattern details.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of breeds to return. Defaults to 10. |
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | Total number of available breeds | |
| breeds | Yes | List of cat breeds |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "limit": 10
+ },
+ {
+ "limit": 25
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "breeds": {
+ "description": "List of cat breeds",
+ "items": {
+ "properties": {
+ "breed": {
+ "description": "Name of the cat breed",
+ "type": "string"
+ },
+ "coat": {
+ "description": "Coat type of the breed",
+ "type": "string"
+ },
+ "country": {
+ "description": "Country of origin",
+ "type": "string"
+ },
+ "origin": {
+ "description": "Origin details of the breed",
+ "type": "string"
+ },
+ "pattern": {
+ "description": "Coat pattern of the breed",
+ "type": "string"
+ }
+ },
+ "required": [
+ "breed",
+ "country",
+ "origin",
+ "coat",
+ "pattern"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total": {
+ "description": "Total number of available breeds",
+ "type": "number"
+ }
+ },
+ "required": [
+ "total",
+ "breeds"
+ ],
+ "type": "object"
+}Input schema / examplesRemoved value: -[
- {
- "page": 1
- },
- {
- "page": 2
- }
-]Output schema / (root)Previous value: -{
- "properties": {
- "breeds": {
- "description": "Array of dog breeds on this page",
- "items": {
- "properties": {
- "description": {
- "description": "Breed description",
- "type": "string"
- },
- "female_weight_kg": {
- "description": "Female weight range",
- "properties": {
- "max": {
- "description": "Maximum weight in kg",
- "type": "number"
- },
- "min": {
- "description": "Minimum weight in kg",
- "type": "number"
- }
- },
- "required": [
- "min",
- "max"
- ],
- "type": "object"
- },
- "hypoallergenic": {
- "description": "Whether breed is hypoallergenic",
- "type": "boolean"
- },
- "id": {
- "description": "Unique breed identifier",
- "type": "string"
- },
- "life_span_years": {
- "description": "Life span range",
- "properties": {
- "max": {
- "description": "Maximum lifespan in years",
- "type": "number"
- },
- "min": {
- "description": "Minimum lifespan in years",
- "type": "number"
- }
- },
- "required": [
- "min",
- "max"
- ],
- "type": "object"
- },
- "male_weight_kg": {
- "description": "Male weight range",
- "properties": {
- "max": {
- "description": "Maximum weight in kg",
- "type": "number"
- },
- "min": {
- "description": "Minimum weight in kg",
- "type": "number"
- }
- },
- "required": [
- "min",
- "max"
- ],
- "type": "object"
- },
- "name": {
- "description": "Breed name",
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "description",
- "life_span_years",
- "male_weight_kg",
- "female_weight_kg",
- "hypoallergenic"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "page": {
- "description": "Page number requested",
- "type": "number"
- },
- "total": {
- "description": "Total count of breeds available",
- "type": [
- "number",
- "null"
- ]
- }
- },
- "required": [
- "page",
- "total",
- "breeds"
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "breeds": {
+ "description": "Array of dog breeds on this page",
+ "items": {
+ "properties": {
+ "description": {
+ "description": "Breed description",
+ "type": "string"
+ },
+ "female_weight_kg": {
+ "description": "Female weight range",
+ "properties": {
+ "max": {
+ "description": "Maximum weight in kg",
+ "type": "number"
+ },
+ "min": {
+ "description": "Minimum weight in kg",
+ "type": "number"
+ }
+ },
+ "required": [
+ "min",
+ "max"
+ ],
+ "type": "object"
+ },
+ "hypoallergenic": {
+ "description": "Whether breed is hypoallergenic",
+ "type": "boolean"
+ },
+ "id": {
+ "description": "Unique breed identifier",
+ "type": "string"
+ },
+ "life_span_years": {
+ "description": "Life span range",
+ "properties": {
+ "max": {
+ "description": "Maximum lifespan in years",
+ "type": "number"
+ },
+ "min": {
+ "description": "Minimum lifespan in years",
+ "type": "number"
+ }
+ },
+ "required": [
+ "min",
+ "max"
+ ],
+ "type": "object"
+ },
+ "male_weight_kg": {
+ "description": "Male weight range",
+ "properties": {
+ "max": {
+ "description": "Maximum weight in kg",
+ "type": "number"
+ },
+ "min": {
+ "description": "Minimum weight in kg",
+ "type": "number"
+ }
+ },
+ "required": [
+ "min",
+ "max"
+ ],
+ "type": "object"
+ },
+ "name": {
+ "description": "Breed name",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "description",
+ "life_span_years",
+ "male_weight_kg",
+ "female_weight_kg",
+ "hypoallergenic"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "page": {
+ "description": "Page number requested",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total count of breeds available",
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "page",
+ "total",
+ "breeds"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "page": 1
+ },
+ {
+ "page": 2
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description doesn't need to restate those. It adds value by mentioning the return fields. However, it fails to disclose that no filtering parameter exists; instead, it implies search-by-name is available, which is a transparency gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the main action, and every word contributes. It is concise and well-structured with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool (one optional param, no nested objects, output schema present), the description is mostly sufficient. However, the unsupported 'search by name' claim makes it incomplete because the description doesn't clarify the actual scope (only limit-based listing) and could lead to incorrect expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage for the single parameter (limit), so the description doesn't need to explain it. However, the description introduces a 'search by name' capability without a corresponding parameter in the schema, which actively misleads the agent about the tool's filtering capabilities.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the primary action (list cat breeds) and specifies the domain (cat breeds), which distinguishes it from unrelated sibling tools. However, it also claims a 'search by name' capability that is not supported by the input schema (which only has a 'limit' parameter), making the purpose slightly misleading.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: to search or list cat breeds. It implies two usage modes (by name or all), but it does not explicitly mention alternatives or exclusions. Given that sibling tools are in unrelated domains, this level of guidance is acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical in routing, differing only in response mode; bet_research and polymarket_edges both surface betting opportunities. Even with detailed descriptions, an agent could easily select the wrong one for a given task.
Tool names are all snake_case, but the pattern is inconsistent: some are verb_noun (get_fact, list_breeds, validate_claim), some are noun/adjective compounds (entity_profile, deep_research, bet_research), and several use a pipeworx_ prefix. There is no consistent verb style or object-first convention.
34 tools is over the 25-tool threshold for a server whose name suggests a narrow cat-facts focus. Only 3 tools relate to cat facts; the rest form a sprawling data platform, creating a severe scope mismatch that makes the count feel excessive and unfocused.
For the cat-facts domain, the set covers the essentials: single fact, multiple facts, and breed listing. However, the overall tool surface is a mix of unrelated capabilities (data lookups, memory, subscriptions, prediction markets) that don't form a coherent domain, leaving the cat-facts portion sparse and the broader set without clear lifecycle coverage.