Skip to main content
Glama

Netbrain Integrated Solutions catalogue

Search the Netbrain catalogue

search_products
Read-onlyIdempotent

Free-text search across every Netbrain product and platform — names, descriptions, capabilities, technologies and tags. Use this to answer questions like "does Netbrain do static analysis for Kotlin", "what can they do for KYC compliance", or "do they have anything for African languages". Returns matching entries with a relevance score, best match first.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for. Free text: a technology, a problem, a product name, or a capability.
listingNoOptional. "product" is a developer tool installed from a public marketplace (JetBrains Marketplace, Open VSX); "platform" is run by Netbrain and is live at its own site or arranged by enquiry.
categoryNoOptional. Restrict results to one category.

Output Schema

NameRequiredDescriptionDefault
resultsYes
matchCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "developer-tooling",
      -  "applied-ml",
      -  "platform-api",
      -  "language-model",
      -  "platform"
      -]New value: +[
      +  "developer-tooling",
      +  "platform-api",
      +  "language-model",
      +  "platform"
      +]
    • changedInput schema / properties / listing / description
      Previous value: -"Optional. \"product\" carries a price in the store and is bought there; \"platform\" carries no price, and access is arranged by enquiry instead."New value: +"Optional. \"product\" is a developer tool installed from a public marketplace (JetBrains Marketplace, Open VSX); \"platform\" is run by Netbrain and is live at its own site or arranged by enquiry."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds that results are ranked, best match first, which is useful behavioral context, but says nothing about result limits, pagination, or what a weak/no-match query returns. Adequate but not rich.

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 verb-plus-resource, followed by illustrative examples and the return shape. No filler and nothing repeated verbatim from the structured fields.

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 full output schema, complete parameter documentation, and rich annotations, the description only needs to convey search scope and intent, which it does. The example queries are a genuine bonus; only edge behavior (empty results, ranking ties) is left 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 description coverage is 100%, with both optional enums (listing, category) fully documented in the schema itself. The description adds no query syntax or filtering nuance beyond what the schema provides, 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 (free-text search) and resource (Netbrain products and platforms), and enumerates the searchable fields (names, descriptions, capabilities, technologies, tags). The scope clearly separates it from single-item siblings like get_product or list_capabilities, though no sibling is named explicitly.

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?

Gives concrete example question shapes that show the intended use case (capability-shopping questions like "does Netbrain do static analysis for Kotlin"). It stops short of any when-not guidance or explicit routing to get_product/list_capabilities, so 4 rather than 5.

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