Tulimoa

Get one SaaS listing

get_listing

Fetch full detail of a single Tulimoa listing by its slug: long description, how it uses AI (ai_usage), features, use cases, integrations, pricing detail, data region and EU hosting, model source, certifications, and links. Use after search_listings when the user wants depth on a specific tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The listing's URL slug, e.g. 'acme-crm'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`listing`	Yes	Full listing row (detail projection, see DETAIL_SELECT).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 28, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "listing": {
+      "additionalProperties": {},
+      "description": "Full listing row (detail projection, see DETAIL_SELECT).",
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "name"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "listing"
+  ],
+  "type": "object"
+}

First observedJun 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Fetch' plus the enumerated read-only payload (description, ai_usage, features, pricing, certifications, links) makes the read-only nature clear and characterizes the response. However, it says nothing about behavior on an unknown/expired slug, permissions, or rate limits, which matters for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with the action and lookup key, then the payload contents, then the routing hint. The middle field enumeration is a bit list-heavy for a tool whose output schema already defines the payload, but nothing is truly wasted.

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?

For a single-record read tool with an output schema and no annotations, the definition covers what it returns and when to call it, so an agent has enough to invoke it correctly. It omits error/miss behavior and any auth expectations, which is a modest remaining gap.

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 description coverage is 100% and the single 'slug' parameter is already documented with format constraints and an example in the schema. The description restates the identifier as 'slug' but adds no format, casing, or resolution guidance beyond what the schema provides, 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 and resource ('Fetch full detail of a single Tulimoa listing') and pins the lookup key ('by its slug'). It is distinguishable from the plural sibling search_listings without opening any 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?

Explicitly routes the agent: 'Use after search_listings when the user wants depth on a specific tool.' That names the alternative and the condition that selects this tool. It stops short of stating when NOT to use it (e.g. for bulk retrieval), so it is not a full 5.

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

All Tulimoa 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.