Skip to main content
Glama

Get a product listing

toolfound_get_product
Read-onlyIdempotent

Fetch the full Toolfound listing for a product by slug: description, tagline, pricing model, tags, socials, vote count, launch date, ownership-verification status, and the canonical listing URL. Every launched listing on Toolfound is ownership-verified by its maker (DNS TXT, meta tag, or domain email). Includes the top alternatives in the same category. Adds verified_metrics when Toolfound has fetched fresh data for the listing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "toolfound_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe product slug, e.g. 'acme-analytics' (from search results or the listing URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the ownership-verification guarantee across launched listings, the bundled top alternatives, and a conditional field (verified_metrics appears only when fresh data was fetched). Return shape is described at a field level, which matters since no output schema exists.

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?

Three sentences, front-loaded with the return contents before the verification and alternatives caveats. Dense but every clause carries information; the enumerated field list is justified by the absence of an output schema. Minor redundancy between "full listing" and the field list.

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?

With no output schema, the description does the necessary work of enumerating returned fields and flagging the conditional verified_metrics field. Overlap with toolfound_get_alternatives is left unresolved, and error behavior for a missing or malformed slug is unaddressed.

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 already documented with an example and origin hints in the schema itself. The description adds only the phrase "by slug," which is baseline-level reinforcement rather than new meaning. No guidance on slug normalization, case sensitivity, or what an invalid slug yields.

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?

States a specific verb and resource ("Fetch the full Toolfound listing for a product by slug") and enumerates exactly which fields come back, so an agent knows this is a detail lookup, not a search. It stops short of naming a sibling such as toolfound_search_tools or toolfound_get_alternatives to sharpen the boundary, and the mention that top alternatives are bundled in sits oddly beside a dedicated alternatives tool without explanation.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must already hold a slug, which the schema hints comes from search results or a listing URL. There is no explicit when-to-use/when-not guidance, no steering toward toolfound_get_alternatives when alternatives are the actual goal, and no note on failure behavior for an unknown slug.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources