Skip to main content
Glama

IA Selecta

by com.iaselecta

Get AI tool detail

get_tool
Read-onlyIdempotent

Fetch the full public detail for one AI tool by its listing slug (as returned by search_tools' toolUrl, e.g. '/tools/acme-writer' -> slug 'acme-writer'). Call this after search_tools to get a tool's full description, launch date, revenue signals (verified or self-reported), and for-sale status. Returns null if the slug doesn't resolve to a live IA Selecta listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe tool's listing slug.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesnull when the slug does not resolve to a live listing on this site.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "tool": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "askingPriceUsd": {
+              "type": "number"
+            },
+            "category": {
+              "type": "string"
+            },
+            "description": {
+              "type": "string"
+            },
+            "faviconUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "forSale": {
+              "const": true,
+              "type": "boolean"
+            },
+            "launchDate": {
+              "description": "ISO 8601 timestamp of the real launch date.",
+              "type": "string"
+            },
+            "logoUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "name": {
+              "type": "string"
+            },
+            "ogImageUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "revenueVerifiedAt": {
+              "description": "ISO 8601 timestamp of the last Stripe verification.",
+              "type": "string"
+            },
+            "selfReported": {
+              "const": true,
+              "description": "Marks selfReportedMrrUsd as unverified. Never report it as verified.",
+              "type": "boolean"
+            },
+            "selfReportedMrrUsd": {
+              "description": "Present only when the figure is the maker's own claim.",
+              "type": "number"
+            },
+            "tagline": {
+              "type": "string"
+            },
+            "toolUrl": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            },
+            "verifiedMrrUsd": {
+              "description": "Present only when the maker connected Stripe.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "tagline",
+            "description",
+            "url",
+            "category",
+            "launchDate",
+            "toolUrl",
+            "logoUrl",
+            "faviconUrl",
+            "ogImageUrl"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "null when the slug does not resolve to a live listing on this site."
+    }
+  },
+  "required": [
+    "tool"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare the operation read-only and idempotent, and the description adds valuable behavioral details: it returns null if the slug doesn't resolve, and it references how the slug is obtained (from search_tools' toolUrl). This clarifies expected outcomes without repeating annotation data, and there is no contradiction.

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?

Three sentences, front-loaded with the main action, each sentence serving a purpose: what it does, when to use it, and edge-case behavior. No fluff or redundancy.

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 a single parameter and an output schema (not shown but present), the description covers the tool's purpose, usage context, return contents, and null case. It is fully self-contained for an agent to invoke correctly within the sibling tool set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only lists 'slug' with a minimal description. The description enriches this by explaining the exact format ('/tools/acme-writer' -> 'acme-writer') and source of the slug (from search_tools' toolUrl), adding semantic meaning beyond the schema's basic type enforcement.

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 clearly states the tool 'Fetch[es] the full public detail for one AI tool' by slug, with a concrete example ('/tools/acme-writer' -> 'acme-writer'). It distinguishes itself from sibling search_tools by mentioning the workflow 'Call this after search_tools', making the purpose specific and unambiguous.

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?

It explicitly instructs when to use this tool ('Call this after search_tools') and lists the type of information returned (full description, launch date, etc.). However, it does not explicitly mention when not to use it or compare with alternatives like list_alternatives or list_offers, so it misses the full 'when-not/alternatives' spectrum.

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

All IA Selecta toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools are clearly distinct: create_checkout, get_tool, list_alternatives, list_offers, search_tools, and submit_tool serve different purposes. However, list_alternatives and search_tools could be confused when searching for alternatives, but their descriptions clarify the target types (well-known tool slug vs. free-text query).

Naming Consistency4/5

Tool names follow a fairly consistent verb_noun pattern: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The only minor deviation is that get_tool is singular while list_* are plural, but this is not a significant inconsistency.

Tool Count5/5

6 tools is well-scoped for a marketplace/directory server with search, detail retrieval, alternatives, paid promotions, and submission. Each tool serves a necessary function without redundancy or bloat.

Completeness4/5

The core workflows are covered: search and view details, list and purchase add-ons, and submit a listing. Minor gaps exist—no update/delete for listings or offers, and no way to manage claims—but these are administrative features outside the main agent use case.

Resources