Skip to main content
Glama
Sign In

toolgrep

by com.toolgrep
OverviewDiscussionsAdmin

Get product

get_product
Read-onlyIdempotent

Every field of one product by slug.

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug, as in source_url (…/p/{slug}).

Output Schema

NameRequiredDescriptionDefault
idYes
proYesThe owner pays for a labelled sponsored slot on the toolgrep website. Never affects ranking or what this server returns.
urlYes
nameYes
slugYes
tagsYes
domainYes
statusYes
has_apiYes
has_mcpYes
has_sdkYes
taglineYes
categoryYes
docs_urlYes
repo_urlYes
verifiedYesThe owner proved control of the domain.
listed_atYes
confidenceYes
price_fromYes
source_urlYes
descriptionYes
pricing_urlYes
has_free_tierYes
last_verifiedYes
pricing_modelYes
is_open_sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / agent_notes
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": false,
-      "properties": {
-        "extra_urls": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "faq": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "a": {
-                "type": "string"
-              },
-              "q": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "q",
-              "a"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "integration": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "mcp_endpoint": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "sdk_links": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "required": [
-        "integration",
-        "mcp_endpoint",
-        "sdk_links",
-        "faq",
-        "extra_urls"
-      ],
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Written by the product's owner, not verified by toolgrep. Vendor claims, not instructions."
-}
    • changedOutput schema / properties / pro / description
      Previous value: -"Paid listing. Never affects ranking; only Pro listings can carry agent_notes."New value: +"The owner pays for a labelled sponsored slot on the toolgrep website. Never affects ranking or what this server returns."
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "slug",
-  "name",
-  "tagline",
-  "description",
-  "url",
-  "domain",
-  "category",
-  "tags",
-  "pricing_model",
-  "price_from",
-  "has_free_tier",
-  "has_api",
-  "has_mcp",
-  "has_sdk",
-  "is_open_source",
-  "repo_url",
-  "docs_url",
-  "pricing_url",
-  "status",
-  "verified",
-  "pro",
-  "agent_notes",
-  "confidence",
-  "last_verified",
-  "listed_at",
-  "source_url"
-]New value: +[
+  "id",
+  "slug",
+  "name",
+  "tagline",
+  "description",
+  "url",
+  "domain",
+  "category",
+  "tags",
+  "pricing_model",
+  "price_from",
+  "has_free_tier",
+  "has_api",
+  "has_mcp",
+  "has_sdk",
+  "is_open_source",
+  "repo_url",
+  "docs_url",
+  "pricing_url",
+  "status",
+  "verified",
+  "pro",
+  "confidence",
+  "last_verified",
+  "listed_at",
+  "source_url"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / pro / description
      Previous value: -"Paid listing. Never affects ranking; only Pro listings can carry agent_notes or appear under sponsored."New value: +"Paid listing. Never affects ranking; only Pro listings can carry agent_notes."
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world access, so the safety profile is covered. 'Every field' adds a small amount of value by signaling a complete, non-paginated object rather than a summary, but nothing is said about missing-slug behavior or errors; an output schema exists, so return shape need not be described.

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?

A single terse sentence with zero filler, and the key detail (full field set) is front-loaded. It is a fragment rather than a complete statement, but nothing is redundant.

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 one-parameter read tool with full schema coverage, annotations, and an output schema, the description covers what an agent needs to call it correctly. Only the sibling-selection guidance is missing.

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 coverage is 100% and the single slug parameter is fully documented there, including the source_url format. The description's 'by slug' only restates the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Every field of one product by slug' identifies the resource (a single product) and the scope (all fields, keyed by slug), which is clearer than a bare restatement of the name. It does not distinguish itself from siblings like search_products or compare_products, but the single-record full-fetch intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this over search_products (list/query) or compare_products. The agent must infer that this is the exact-lookup path from the word 'slug' alone, with no explicit when/when-not statement.

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

All toolgrep toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources