Skip to main content
Glama

BlockSentient directory tools

Get one product

get_product
Read-onlyIdempotent

Returns one product's full published record: plans and prices, documented compliance and data rights, CTI score with its breakdown, features, FAQ, the date its facts were checked, the vendor pages they came from, the official site and a visit link.

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": {
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct ID from search_products

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by itemizing what the returned record contains, including the fact-check date and vendor source pages — information an agent needs to decide whether this tool answers its question. It says nothing about pagination, size, or behavior for unknown IDs, which is the remaining gap.

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?

One front-loaded sentence: the verb and resource come first, then the field enumeration. The long list is justified because no output schema exists, though a few items ('the official site and a visit link') could be compressed.

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 a single required parameter, full annotation coverage, and no output schema, the description's field enumeration carries the return-value burden adequately. It omits error/null behavior for a bad ID, but everything needed to call the tool correctly is present.

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 'id' parameter is documented in-schema, including its origin from search_products. The description adds no additional meaning about the parameter (format, validity, or error behavior), 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?

States a specific verb ('Returns') and a precise resource ('one product's full published record'), then enumerates the record's contents. The 'one product' framing implicitly contrasts with a list/search tool, but no sibling is named, so differentiation is inferred rather than stated.

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?

No explicit when-to-use or when-not-to-use guidance appears in the description body. Usage is only implied by 'full published record' (fetch details once you have an ID), and the ID's provenance lives in the schema ('Product ID from search_products') rather than the description.

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