Skip to main content
Glama

Open Agent Guide

Get Product

get_product
Read-onlyIdempotent

Fetch one catalog product by UUID or slug with its AI-native scores (ai_native_score 0-100, ai_native_tier S/A/B/C/D) and related organization, capabilities, and integrations (MCP servers, SDKs with languages and licenses, CLIs, A2A servers, API specs, plugins) expanded inline as objects. Also returned: a second research-coverage axis — coverage_score (0-100) and the derived boolean unrated. Coverage tells you how thoroughly the product was researched before you trust the grade; unrated is true when research coverage is too low to assign a letter grade (present as "Unrated / needs research"). Plus the always-present attested_absences list — fields a dated check attested absent (each a field_key or field_key:label for a relation-scoped negative), the read booleans has_mcp, has_mcp_url, has_sdk, has_api_spec, has_cli, has_a2a (each reads back its filter), and free_plan (True for an active free-tier offer, else null; never false). has_mcp_url is true when a cataloged MCP server has a dialable endpoint URL. It is false when no MCP endpoint URL is cataloged.

documented_task_completions contains all assessed jobs. Match each selected job to job_to_be_done_slug or job_to_be_done_id. Show its verdict, scope, and conditions with its assessment. The verdict includes delegation limits. No matching record means unassessed; a matching record with null completion_support means unknown. Neither establishes inability to complete the job. Keep other jobs secondary. If you use fields, include documented_task_completions.

The identifier is forwarded to the canonical {id-or-slug} detail route, which owns the missing/ambiguous/invalid errors: an unknown value is 404, a slug matching multiple products is 409, a malformed slug is 400 — each a structured tool error with the catalog's code and detail, consistent with get_product_coverage. fields trims the payload; the default affordance relations are still expanded.

A missing or unknown value is JSON null on every field type — the nullable booleans, the status enums (MFA, data-retention, sandbox, portability), and the URL/text fields alike — so never read a blank as a negative; the real negative is always explicit (false, or no/none/unavailable). attested_absences then flags which negatives are cited: listed is a cited "no", an explicit negative not listed is recorded but uncited, and a null is unknown. The full attestation records (method, source_url, checked_at) are not returned by default; pass expand=absence_attestations to include them, and use expand to resolve any other relation *_ids into inline objects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for product, matching the REST {id-or-slug} route. Accepts a UUID or slug.
expandNoComma-separated product relations to expand inline beyond the affordance and documented_task_completions relations this tool always expands, following the REST ?expand= grammar. Example: compliance_certifications,offers,absence_attestations. Your values are added to the defaults, so name only the extras. An invalid value returns the allowed set.
fieldsNoComma-separated top-level response fields to include, following the REST ?fields= grammar. The response always keeps id. Narrows the payload for compact reads; an expanded relation is still returned only when its field is in the selection. Omit for the full record.
productNoThe product's UUID or slug.
product_idNoLegacy UUID-only argument. Use product instead.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavioral context: the 404/409/400 error contract delegated to the detail route, the null-vs-explicit-negative rule ('never read a blank as a negative'), ``free_plan`` never being false, ``has_mcp_url`` semantics, and what ``attested_absences`` cites versus omits. That is real disclosure an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads purpose well, but the body sprawls into long backtick-dense paragraphs and the most operationally important rule (null is never a negative) is buried mid-text after the ``documented_task_completions`` digression. It reads like API documentation pasted in, with several sentences that could be tightened without losing meaning.

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 read tool with full annotations and an output schema, this covers nearly everything an agent needs: identifier routing, expansion, field trimming, error codes, and null/absence semantics. The only shortfall is redundancy — much of the text re-explains return fields that the output schema already owns.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds interaction semantics the schema alone does not convey: ``fields`` trims the payload while default affordance relations are still expanded, ``expand`` values are additive to the defaults, and the requirement not to drop ``documented_task_completions`` when trimming. It does not, however, resolve the ``id``/``product``/``product_id`` aliasing beyond what the schema already says.

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?

Opens with a specific verb and resource ('Fetch one catalog product by UUID or slug') and immediately scopes it as the single-record read, which contrasts cleanly with the plural siblings like search_products and list_*. The enumeration of what comes back (AI-native scores, capabilities, integrations, coverage axis) leaves no ambiguity about what this tool is for.

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 implied rather than stated: an agent infers it should call this when it already has an id or slug, and the text gives operational rules ('If you use ``fields``, include ``documented_task_completions``', 'use ``expand`` to resolve any other relation ``*_ids``'). But there is no explicit when-to-use versus when-not guidance against search_products or get_product_coverage, and the get_product_coverage mention is only about error-code consistency, not routing.

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